Clarity

HI,

We have a Job that loads the company information into Clarity.

I am seeing below error when in logs when Job starts 

query.ObjectDelegate (clarity:admin:14091700__6E04F694-DB40-4B5B-B87E-9D3C623B88FF:bizdev.companyList) Attribute specified in policy (id) not part of object - company

Can anyone please advise on this error  and how to solve this?

Regards,

Divya

Hi Divya

Is your job a Java job or does it use XOG to insert the data? If it's XOG make sure the attributes are standard and existing on the company object. For both I'd suggest opening and looking at the code to see what it is trying to update and what fields it's mapped to.

Hope this helps -Nika

Hi Nika,

Yes it is a Java Job and does Xog to insert the data.

I have checked the code and all attributes looks fine.

Also, when I run it locally in Eclipse, data gets loaded to Clarity. However, when the same job is run from Clarity UI, I see this error.

Regards,

DIvya

Can you try getting the XOG and xogging it manually and see if it works?

Hi Nika,

I did try that. It simply works fine when Xog it manually.

Regards,

Divya

When things like this happen to me. I normally run the services in debug mode and attach intelliJ (eclipse) with a break point in my job.  This allows me to catch the exception and look and the stack.

Look in the PPM bin directory for serviceNAMEcmd-debug.conf.  Set the debug port -- I think the OOTB is 5055.

Spin up the services in debug via the serviceNamecmd-debug.exe, run the job via the UI and see what is happening.

V/r,

Gene

HI Eugene,

I am Sorry that I have no idea on  how to perform your below suggestion.

I did look into the debug files and did not find the entry for Debug port.

Could you please tell me how to perform this?

Look in the PPM bin directory for serviceNAMEcmd-debug.conf.  Set the debug port -- I think the OOTB is 5055.

Spin up the services in debug via the serviceNamecmd-debug.exe, run the job via the UI and see what is happening.

Regards,

Divya

In the bin directory you will find the servicebgcmd-debug.conf file.  In the config file it set the following JVM options for the background server.

wrapper.java.additional.9=-Xdebug
wrapper.java.additional.10=-Xnoagent
wrapper.java.additional.11=-Djava.compiler=NONE
wrapper.java.additional.12=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005

Once you start the bg server using this conf file, you can attach the eclipse debugger to port 5005.  When the bg server executes your job, it should break on any point you have set.

I used this method when I was debugging my job to run Gel Scripts.  I don't use eclipse but here is my debug settings for IntelliJ.

V/r,

Gene