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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Supply chain | Supply Chain Management, Commerce / Best practice warnings...
Supply chain | Supply Chain Management, Commerce
Answered

Best practice warnings - front end view

(1) ShareShare
ReportReport
Posted on by Stephen King 86
Good day
 
I'm currently working on a tool similar to this one by Alex Meyer:
 
I'm showing the custom objects for each custom model. I was wondering if it's possible to retrieve the best practice warnings (see sample screenshot from visual studio below) after a model is built and display these on the front end. 
 
 
Overall goal: a quick front end view of the custom models that exist in an environment (this part is done) and some information about the quantity and types of best practice warnings so as to give some sort of indication as to whether best practices have been followed. 
 
Any advice would be greatly appreciated. Thanks
Categories:
Dynamics 365 Supply Chain Management
I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at
    You can't find this information inside F&O. The information is generated during compilation, but it's not stored the resulting application files. It's not needed to run the application (unlike the application objects in Alex's blog post) and it's not something to share with end users, therefore it's not included in a deployment.
     
    I wouldn't share that with end users, but you really want, it can be done. You need to collect the data after compilation (most likely in a build pipeline), store it somewhere where F&O can reach it and then you can present it in F&O.
     
    I built something similar, but I didn't show the data inside F&O. My approach was following:
    1. I was interested in compiler warnings, BP deviations and TODOs. You can let the compiler generate XML files with this data.
    2. I configured a build pipeline to include these files in a resulting artifacts.
    3. I had a Power Automate flow running on a successful build, which combined the files (for easier processing), stored the file in a blog storage, extracted some basic information (e.g. the number of warnings) and store it in an Azure table.
    4. Then I built a Power App showing this data to developers and other stakeholders (it had a grid with information about every commit, a button to download the full log and a button to compare two logs).
    Of course, you could modify this process. You could embed the Power App in F&O, create an F&O customization for reading the data from Azure, write the information directly to F&O instead of Azure storage or so.
  • Stephen King Profile Picture
    Stephen King 86 on at
    Thanks very much Martin. 

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…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Laurens vd Tang Profile Picture

Laurens vd Tang 298 Super User 2025 Season 2

#2
Siv Sagar Profile Picture

Siv Sagar 179 Super User 2025 Season 2

#3
André Arnaud de Calavon Profile Picture

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

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans