Microsoft Dynamics 365 | Integration, Dataverse...

BPF Header fields do not appear in controls collection

(0) Share

Report

Posted on by Gary Cook

180

Hi,

I have a very interesting and confusing issue with regard to the "header_process......" controls not appearing in the control collection when using UCI and V9.0.16 (On Premise).

What makes this issue even more confusing is the header_process controls are only missing for the "system administrator" in one of my environments

I currently have checked in two environments a DEV and QUA environment, and with a system admin and non system admin user and on all browsers

I have checked on multiple BPFs and on existing and new records

In my DEV environment I have an onload function in javascript which gets the context , if I put a break in after I get the context and check the controls I do not see any header_process controls (but only for system admin).

If it was the other way around I would have thought it could have been a security issue , but sys admins have access to everything

So using F12 I break in my OnLoad method and use the following to check the controls

exeContext.getFormContext().ui.controls

Just wondering if the community has seen this or has any idea how I can further investigate

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Henry J. 5,237 on at

Like (1)

Report

Hi Gary,

I haven't seen this issue in the past, but Unified Interface on Dynamics 365 Customer Engagement v9.0 on-premise is very limited and it has a lot of parity gaps or even issues that have been fixed online.
I'm curious as to why you would want to deploy it on-premise and not use the web client instead?

Regarding this specific issue, I advise that you check with support:
https://mbs.microsoft.com/customersource/global/CRM/support/support-lifecycle/CRMSupport

Henry

Was this reply helpful? Yes No
Gary Cook 180 on at

Like (0)

Report

Thank you,

Our customer insisted that we upgrade them from 8.2 to V9.0 On Premise using UCI. They have to be on premise for data governance and they wanted UCI because their internal people have seen the Classic deprecation communications. We advised against it but your customer has the final say. I will check with support on the issue

Was this reply helpful? Yes No
Suggested answer

Henry J. 5,237 on at

Like (0)

Report

Thank you Gary, and I fully agree with the recommendation you made.

It's important that your customer understands that the web client on Dynamics 365 Customer Engagement on-premise is NOT deprecated.
This is specifically called out here:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/faqs-transition-unified-interface#how-does-this-move-impact-on-premises-customer-and-what-will-happen-when-the-web-client-is-deprecated-do-web-client-forms-become-unsupported
So the web client will still be supported for them, as long as the V9.0 version is supported. Support lifecycle for every product is detailed here: https://support.microsoft.com/en-us/lifecycle/search

Your customer and especially end users might be confronted with limitations and issues in their usage of UCI apps on V9.0 on-premise.
If they are going to stay on-premise, it might really be best to wait for a next on-premise version that contains an updated version of Unified Interface.

Was this reply helpful? Yes No