Finance | Project Operations, Human Resources, ...

Rest API for Data Entities Contactsv2 and General Journal

(1) Share

Report

Posted on by Community member

Hi All,

We are trying to integrate into D365 Contact Data and General Ledger transactions from custom developed apps. We believe the data entities to use for Contact Data is 'Contactsv2' and for General Ledger Transactions it is 'General Journal'.

However, when trying to get the rest endpoint using the URL https://[d365 URL]/data/ContactsV2? we get the message....

<Message>No HTTP resource was found that matches the request URI 'https://[d365 URL]/data/ContactsV2'. No route data was found for this request.</Message>

Similar situation for General Journal using the URL https://[d365 URL]/data/GeneralJournal?

We have checked the data entity meta data and notice these two entities are not referenced in there. I have refreshed the data entity list in D365 as well.

Using these entities in D365 F&O data management we can import and export both contact data and general journal data without issues, but we are looking to integrate via the odata rest api

Any idea if these are the correct data entities to use if we integrating via and rest api or what the issue may be causing the error.

Bijal

I have the same question (0)

All responses (6)

Answers (0)

Layan Jwei 8,112 Super User 2025 Season 2 on at

Like (0)

Report

Hi User,

I'm assuming you are trying to use odata.

Are u calling this url via postman? If that's the case, then can you please provide us with screenshots of how are u calling it so that we can help? As you need to fill few things in the body like resource, grant_type, client_id and client_secret

Best Regards,

Layan Jwei

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 301,030 Super User 2025 Season 2 on at

Like (0)

Report

Hi Bijal,

You must use the public collection name of the data entity for OData. In this case, the contacts entity is PartyContactsV3 (V3 is a newer version compared to V2). What exact are you expecting by using the general journal? Do you want to upload journal lines? In that case, you can use the entities LedgerJournalHeaders and LedgerJournalLines.

Was this reply helpful? Yes No
Community member 8 on at

Like (0)

Report

Thanks Andre.

I will look at using the PartyContactsV3 for loading contacts data, thankyou so much for the direction.

In terms of, General Journal, yes we are looking upload journal lines. However I can not see these entities in D365 F&O Data Management. I believe I need to set the appropriate setting as described in https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/tips-tricks-import-general-journal-entity i.e 'set based processing' at the data entity level.

Looking at the meta data for the journal header and journal lines, I can see the value D365 F&O data management set to 'false', presuming this is why I can not see it in F&O. Appreciate your thoughts....

Appreciate your thoughts.

Was this reply helpful? Yes No
Suggested answer

dickson kimeu 249 on at

Like (0)

Report

I have a similar requirement,

I implemented custom services.

Was this reply helpful? Yes No
Martin Dráb 237,880 Most Valuable Professional on at

Like (0)

Report

The topic of this thread has nothing to do with custom service, therefore don't expect any response here. Instead, create a new thread and explain your problem there.

Also, please don't mark such comments as suggested answers. You reply clearly contains no answer to Bijal's question.

Was this reply helpful? Yes No
Hirof 7 on at

Like (0)

Report

The error message you provided suggests that the endpoints for these entities, including "company information API," may not be accessible or configured correctly. Here are some steps to troubleshoot the issue:

Ensure that you are using the correct entity names. Entity names in Dynamics 365 are case-sensitive. Double-check the entity names and make sure they are spelled correctly.

Not all data entities are available through the OData REST API. Some entities might not be exposed by default. It's possible that 'Contactsv2' and 'General Journal,' including "company information API," are not accessible through OData. You should confirm the availability of these entities for OData access.

Ensure that the user or application trying to access these entities, including "company information API," via the REST API has the necessary permissions and privileges in Dynamics 365. You might need to configure security roles and permissions to allow access to these entities.

Was this reply helpful? Yes No