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

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

RecId field not present in standard entity

(0) ShareShare
ReportReport
Posted on by 8,201

 Hello,

 I want to know, is there a reason why MS didn't include the RecId field in the standard entities (of course I did not look at all the entities, now I am working with the EcoResReleasedDistinctProductV2Entity)?

 Just to be clear on what I want: a lot of APIs on the CSU require the product RecId, and I would get these recids from the dataverse dual-write enabled tables; but since I have no RecId in the FO entity in the first place and I do not want to extend the entity, I am wondering why this data was not included by default?

I have the same question (0)
  • Israel Gonzalez Profile Picture
    733 on at
    RE: RecId field not present in standard entity

    As I said.

  • Verified answer
    Martin Dráb Profile Picture
    236,233 Most Valuable Professional on at
    RE: RecId field not present in standard entity

    If you need it, you can add RecId to a standard entity (via an extension), or create a new entity for your purposes.

  • Iulian Cordobin Profile Picture
    8,201 on at
    RE: RecId field not present in standard entity

    Commerce Scale Unit.

  • Iulian Cordobin Profile Picture
    8,201 on at
    RE: RecId field not present in standard entity

    Hi all,

    Thanks for your answers.

    I do agree with the statement that integrations should use natural keys.

    But, now the question comes: if the API exposed by the CSU breaks this pattern, is it ok? The endpoint Commerce/Products/GetEstimatedAvailability requires (only) the RecId of the Product.

  • Martin Dráb Profile Picture
    236,233 Most Valuable Professional on at
    RE: RecId field not present in standard entity

    Record IDs aren't supposed to be exposed to external systems and people. RecId are considered an internal detail of F&O; natural keys (such as product numbers or customer IDs) should be used for communication with other systems.

    This should explain why entites normally don't expose RecId and why it's considered a bad practice.

    Your need to use them suggests that someone didn't respect the pattern.

    What is CSU?

  • Verified answer
    Israel Gonzalez Profile Picture
    733 on at
    RE: RecId field not present in standard entity

    Hi Lulian,

    I recomend you create a new custom entity with the fields you want, that is the way if you need some fields like RecId, dataAreaId, etc.

  • Verified answer
    GirishS Profile Picture
    27,825 Moderator on at
    RE: RecId field not present in standard entity

    Hi Iulian Cordobin,

    There is some RecId field available in standard entities. Refer to the entities like DirPartyBaseEntity where you will have RecId of LogisticsElectronicAddress table (PrimaryContactEmailRecordId). For some entities they didn't add that one, if you want you need to add that via extension.

    Mostly data entities will be used in open in excel or some other integration purposes, so I guess instead of adding RecId values they have added the values that will be more in more readable format.

    Thanks,

    Girish S.

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…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

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

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 2,258

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 631 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans