Finance | Project Operations, Human Resources, ...

Updating Jobs - how do I find ObjectID?

(0) Share

Report

Posted on by TechLogic

I'm developing a logic app that needs to update one or more records in the Jobs entity in dynamics.

When updating a record in the entity, I'm required to provide an ObjectId which I'm not sure what is and where to find it.

In my search I was able to find someone who said it consists of the company's data area id and an account code, separated by a comma. I'm unable to find either of those and I'm not even sure that it's what I need.

Info/documentation is really sparse on this area so by all means, point me in direction of some documentation.

Where and how do I find the needed ObjectId for updating rows in a dynamics entity?

- Anders

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Rahul Mohta 21,042 on at

Like (0)

Report
Copy link

Link copied!

pls see if this helps

https://community.dynamics.com/ax/b/happyd365fo/posts/logic-apps-with-microsoft-dynamics-365-finance-and-operations

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report
Copy link

Link copied!

Hi TechLogic,

The ObjectId is the unique identifier of the object.

What you need is the DataAreaID and JobNumber sans quotes.

calafell.me/.../

Was this reply helpful? Yes No
TechLogic 25 on at

Like (0)

Report
Copy link

Link copied!

I've read these posts, but when I try to apply it I get: "Only 2 of 1 keys provided for lookup, provide keys for JobId".

For testing purposes I get the record before I try to update and I'm passing the JobId from the "Get record" action to the "Update record" action. So as to why it say I'm not providing JobId, I don't know.

EDIT: Spelling

Was this reply helpful? Yes No
Suggested answer

TechLogic 25 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the help.

After reading your provided articles along with this one dynamicspedia.com/.../, I was able to get it to work. It seems that the job entity doesn't need to specify DataAreaID, only the JobId hence the "Only 2 of 1 keys provided" as it only needs one - the JobId.

My second issue was that when I got it to work I wrongfully set Expiration and Effective to utcNow(), which obviously would immediately make the update and expire at the same time.

So when setting Expiration to never, Effective to utcNow() and only using the JobId for updating the record, I finally got it to work.

Thanks for the help

Was this reply helpful? Yes No