web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Updating Jobs - how do I find ObjectID?

(0) ShareShare
ReportReport
Posted on by 25

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)
  • Suggested answer
    Rahul Mohta Profile Picture
    21,032 on at
  • WillWU Profile Picture
    22,361 on at

    Hi TechLogic,

    The ObjectId is the unique identifier of the object.

    What you need is the DataAreaID and JobNumber sans quotes.

    calafell.me/.../

  • TechLogic Profile Picture
    25 on at

    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

  • Suggested answer
    TechLogic Profile Picture
    25 on at

    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

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 559 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 464 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 250 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans