Skip to main content
Post a question

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id : 5oTu2zy4jLJ2mNAAXZtk+v
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

Like (2) ShareShare
ReportReport
Posted on 31 Jan 2025 14:29:03 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
  • Stephen King Profile Picture
    Stephen King 86 on 31 Jan 2025 at 17:31:50
    Best practice warnings - front end view
    Thanks very much Martin. 
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 231,305 Most Valuable Professional on 31 Jan 2025 at 15:04:27
    Best practice warnings - front end view
    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.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,489 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,305 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans