PX behaves differently on server
What is happening is that the attributes called in the PX are recognized when the PX runs locally (on developer’s computer) but not when the PX is run automatically on the Agile server. When the PX queries the table for Manufacturer and Compliance Required information the values returned locally and from the server are different. Locally they are the correct values and from the server they are “null, null”. How can this happen? Can this be due to the attribute naming in the PX?
A couple of things to check:
- Is your local execution connecting to the same Agile server as your PX on the server?
- Are you sure the server copy that is being run is the same version. On Linux machines the old jar can be cached and you would then need to restart weblogic to reread the jar.
- Make sure you do not put the AgileAPI.jar into the extensions folder on the server.
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.
check listL
– same server, same id/role being used?
My old mistake where the PX was triggered via Event used different privilege ( assigned to the user ) than the “test” credential used during locally ran tests,
