Hi Kulbhushan,

The “Part” is pretty generic API name that is used for creation however that shouldn’t stop you from creating a part.  Also the fact that you are able to create part it means there is some issue with the Map object you have.

I used similar kind of syntax and it worked pretty fine for me:

//m_admin.getAgileClass(partType[i]).getAPIName() fetches the API name for a particular subclass.
//newAutoN : Is the AutoNumber source for my particular part type

IDataObject m_item = (IDataObject)m_session.createObject(m_admin.getAgileClass(partType[i]).getAPIName(), newAutoN);

Can you share the structure of Map you have and the attributes which you are trying to set. Also as a troubleshoot you can try to Create part fast and then set values just to isolate the issue.

Regards,
Arif

You are implying that existing PXs are configured without loggers or SOPs or you need additional logging apart from log4j. If the later to be true then i suggest going to
Administration >> Logging Configuration and see if you can use additional logging option.  Note, these settings gives you logs based on the Jars on Core-APIs not sure how much they will help you on custom PX.

Agree with Kevin here, OOTB Import doesn’t support appending values and writing a Macro by concatenating existing values with expected values will do the work. 

Also, you can develop simple SDK based utility to read the excel file and append the values to Agile Object. Which you can reuse in future as well. Let me know if you need any help with that.

Hi Sai,

What kind of PX you are writing.  You can use log4j to generate logs as per your wish. Sharing a quick snippet from my code.  You can place it before your  ActionResult method and test.

public static Logger logger = null;

static {
try {

InputStream ins = YourJavaClassName.class .getResourceAsStream(“/properties/Log4j_MyPX.xml”);

            new DOMConfigurator().doConfigure(ins, LogManager.getLoggerRepository());
          logger = Logger.getLogger(YourJavaClassName.class);
}
}

Regards,
Arif

Hi Sandeep,

This might sound a bit basic but can you cross verify few things:

1.  Verify your Event class name entry in file –>  META-INF/services/com.agile.px.IEventAction file.
2. If you are running a clustered environment, can you check if you have deployed the same version on extension folders of all the nodes.
3.  At times i have faced similar issue in Java-client so what i do is i either login to one of my file server and try to launch Java-client there OR
Clear temporary files form Java Control Panel and it works.

Regards,
Arif

Hi Kaustabh,

I don’t think there is one such procedure or utility to depict the relationship in Agile schema as such.  However there are many more threads in our community containing queries for key data from Agile. You can review them and use it as per convenience.

I suggest you to go through the below post to start off then there are other specific queries that you can utilize.
https://myagileplm.com/questions/how-to-start-db-learnings/

Agree with Steve here, faced similar situation. I have seen issue specifically with Manufacturer Parts and Manufacturer Page Two attributes when we upgraded to 9.3.5. We worked with Oracle to get a patch 9.3.5.2 where the issue was fixed.

So just double check your connection parameters and AgileAPI you have configured in your sdk project with server.

Agree with Steve here. You can build a sdk based utility and use generic mail apis to configure such notification.

Hi

A part of this is possible but not advisable. If something breaks in the process then Oracle won’t support your there. Creation of any kind of objects starting from Item to Change and others require data manipulation in multiple tables so not a safe approach.

Coming to update part, It is possible and i personally have done it quite a few times. To proceed with that you need to test it thoroughly in your non-prod environment. To state a few updates i tried as test is Page-Two,Page-Three  values, status change, User group name changes etc, they worked fine. At times they require a bit of time to reflect on front-end after you update them from back-end. Still i try to avoid this from back-end unless i have no choice.

So for Create personally Not Advisable, for Update proceed with caution is what i can suggest.

Regards,
Arif