Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Std field expose in en...
Finance | Project Operations, Human Resources, ...
Suggested answer

Std field expose in entity

(0) ShareShare
ReportReport
Posted on by vicky1234 498
Hi,
 
I am using the entity AOT name /CustCustomerV3Entity/ and public name is /CustomersV3/.
I am able to use GET and POST commands via POSTMAN.
 
I wanted to filter the records based on the field /CreatedDateTime/ however this field is not exposed in the fieldlist of the /CustomersV3/ entity and if I try to add the field I get the below error which states that CreatedDateTime cannot be used however if I rename it to CreatedDateTime1 then i am able to use it.
 
 
Interestingly if I do a sql query with entity name I am able to fetch the data and use the field /CREATEDDATETIME/.
/select CREATEDDATETIME,* from CustCustomerV3Entity/
 
I want to filter the data based on 'CREATEDDATETIME' via POSTMAN . Can you please suggest what is the best way and why are the system fields not accessible via postman.
I know if I add these fields in the fields node of the entity then I can use them but then the problem is that I need to rename them to any name other than /CREATEDDATETIME/.
Client wants to use the same name.
 
Same applies to other std fields.
 
Thanks,
Vikas
  • vicky1234 Profile Picture
    vicky1234 498 on at
    Std field expose in entity
    hi Martin,
    thanks for the reply.
     
    Also 1 more query is that whenever there is a call to the entity there are some mandatory fields which are required, however at entity level  some are kept with property as "Auto" and then too they are mandatory, I think they inherit the value from the corresponding table , however the problem over here is that the entity metadata shows Mandatory fields only for the Mandatory property as yes and for Auto it shows as No for mandatory section.
     
    Is there a way I can find out which all fields are actually mandatory or is there a reason for them to keep the field as "Auto" for mandatory property even though that fields needs to be mandatory.
     
    Thanks again for your reply.
     
    Thanks
    Vikas Mehta.
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 230,235 Most Valuable Professional on at
    Std field expose in entity D365 FO
    The client will have to accept that CreatedDataTime is reserved and you can't create custom fields with such a name. You must use a different name.
     
    By the way, don't forget that the entity takes data from several tables. The fact that CustTable.CreatedDateTime didn't change doesn't necessarily mean that the entity record returns the same data. For example, the primary address of the customer might have changed.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans