Wrong field is mandatory for D365 FNO connector for entity ItemArrivalJournalHeadersV2

Linus Waerner 6 Reputation points
2023-01-09T09:47:22.6+00:00

Hi,

It has come to my attention that we're unable to create records of ItemArrivalJournalHeadersV2 using the designated Logic Apps connector, when the number series is managed by D365.
Using the connector the OData field "JournalNumber" is mandatory. If I omit it, it breaks and D365 throws an error, but, if I use the HTTP connector it all works out as intended and the number is being automatically set.

Is this by design? I really want to stay consistent and use the designated FNO action/adapters, but for this particular entity I have to use a HTTP action and configure it for OData.

Please advice :(

Best regards,
Linus

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
3,313 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.