Finance | Project Operations, Human Resources, ...

Best practices to be follow in integeration like Logic app, power automate

(4) Share

Report

Posted on by CU05031448-0

1,275

Dear team,

Pls let me know what are the best practices to be follow in integeration like Logic app, Power automate with D365FO.

Kindly explain pls.

Thanks in advance.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (8)

Answers (0)

Martin Dráb 237,801 Most Valuable Professional on at

Like (0)

Report
A common mistake I see that people start working on an integration with the first API they find, without asking many important questions and then choosing a solution suitable for the actual requirements. Here are a few examples:

What should happen the target systems can't be reached, e.g. because F&O is down for maintenance, due to a failure or so? Is it fine to lose the messages, will the source system resend it, should there be a message queue in between...? Should the source system be able to continue or is it a blocking issue?

How many request will be sent in peak times? Won't it negatively influence performance or won't messages be rejected by throttling policies? Maybe we should use something like a message queue instead of direct requests - when there are more requests than can be processed immediately, it just mean a longer queue, not overwhelmed system or rejected messages.

How much data will be sent? Some APIs are suitable for large volumes; you may want to use data management APIs instead of the usual connectors.

Will a response be needed? What data do you need to extract? Will you wait for a response or will it be done asynchronously, e.g. a business event will be raised when the processing is done?

Was this reply helpful? Yes No
Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

Martin has mentioned about data volumes already.

Dual-write is a common use these days at many organizations. I have seen projects where people have been sleepy to observe dual-write live synch limits and designed the solution wrongly.

Be aware of those, especially 1000 lines limit issue.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (0)

Report

Thanks for the response.

Honestly speaking, not understand Martins reply.

Kindly elaborate pls.

Thanks in advance

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

Like (0)

Report

Please be more specific about what you don't understand.

You may need to learn more about the design of distributed systems before you can design the solution on your own, but statements like that you should know the expect amount of data shouldn't be difficult to understand. Therefore I'm assuming that you're struggling just with some parts of the reply, not all, and you merely failed to specify which ones.

Was this reply helpful? Yes No
Raj Borad 1,424 on at

Like (0)

Report

Hi @CU05031448-0,

There are various common things related to Audits data and security which should be maintain during the integration.

1. Use Standard available Data entities.
2. Monitor performance and data validations.
3. Don't try to manipulate the inventory, transactional, or financial data which affects the business logic.
4. Use security roles for data changes in FO

It depends based on the integration.

Thank you,

Raj D Borad

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (0)

Report

Thanks Raj fr the response.

Kindly elaborate point 4 pls.

If I like to do recurring integeration for inbound and outbound with API. Which security role I have required.

Thanks in advance

Was this reply helpful? Yes No
Sagar121 827 on at

Like (1)

Report

Let me add some more context here:

When using Power Automate (Flow), it's important to implement try-catch blocks for proper error handling.
Especially, learn about the "Scope" action — it's a key concept for structured error handling.

Also, it's a good practice to create an extra field or send an email for logging whether the transaction was fully completed or not.

Make sure to train the IT team for unexpected downtime.
You should also include common troubleshooting steps in your documentation.

Use connectors wisely — avoid using personal authentication.
Instead, try to use a Service Principal. To set this up, you may need to coordinate with your IT team.

Developing flows and logging apps is relatively easy, but training others for support is equally important.
Integration can fail at any time, so having logging fields and failure notification emails is a best practice based on my experience.

If you're using Power Automate, make sure you're monitoring API limits.
If you're using Logic Apps, check your Azure subscription and decide which type of Logic App (Standard or Consumption) is best suited for your needs.

Was this reply helpful? Yes No
Suggested answer

Sagar121 827 on at

Like (1)

Report

@CU05031448-0 Do you have any other questions here?

Was this reply helpful? Yes No