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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Day to Day Dynamics 365 / Dynamics 365 Project Servic...

Dynamics 365 Project Service Automation: Do not use legacy form rendering with PSA

apa Profile Picture apa 8,284 Moderator

Tested on:
Dynamics 365 version 8.2 and 9.0


Microsoft Dynamics CRM Online 2015 Update 1 (v7.1) introduced a new form renderer to provide better performance. With that, an organizational-level fallback was also introduced to temporarily allow usage of the legacy rendering engine. I recently ran into strange behavior on several entities when I was configuring Dynamics 365 Project Service Automation. For some reason the following issues appeared:

  • Create Invoice button on ribbon was occasionally at an incorrect position without any functionality behind it. Reloading the form occasionally corrected the issue.
  • Create Invoice Schedules button on ribbon was occasionally missing completely. Reloading the form occasionally corrected the issue.
  • Unrelated records were displayed on several different subgrids. Unrelated records were visible on Quote Line Details, Order (Project Contract) Line Details, Invoice Line Details and Invoice Schedules.

Incorrect-ribbon-_2D00_-order-entity.png
Create Invoice is at an incorrect position. It should be 5th from the left on an OOTB ribbon. The ribbon is also both missing buttons and containing unrelated buttons.


Incorrect-ribbon-_2D00_-order-entity.png
Create Invoice Schedule button is missing on the ribbon. The ribbon is also both missing buttons and containing unrelated buttons.



Legacy-Forms-_2D00_-unrelated-records.png
Several unrelated records are displayed on Project Contract Line Details. This occurs on several other entities as well.


Solution

With Microsoft's fantastic help it was identified that legacy form rendering causes the issues with the ribbons. Setting legacy form rendering to "No" also solved the issue with unrelated records being displayed. The conclusion is that legacy form rendering must be set to "No" so that these issues do not occur. This applies to Dynamics 365 Customer Engagement version 8.2 as well as 9.0.

LFR.png


Disclaimer: 
All my blog posts reflect my personal opinions and findings unless otherwise stated.

Comments

*This post is locked for comments