Model-Driven App: setting default value for lookup field not possible

(0) Share

Report

Posted on by cantareroj

Hi Guys,

I need help regarding the following problem:

Under Model-Driven App I want to set a default value in a lookup field when form is created. I used the following solution as a recommended approach, using a Business Process Flow:

The condition is quite simple and it works fine:

...but when I try to select some default value for the lookup field, then no list of values are shown:

Note: The table has values!!!.

If I select another view, then I get an error:

System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: <internalservererror>Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. If you contact support, please provide the technical details.</internalservererror> (Fault Detail is equal to Exception details:
ErrorCode: 0x80040216
Message: <internalservererror>Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. If you contact support, please provide the technical details.</internalservererror>
TimeStamp: 2023-08-31T10:52:40.6173870Z
--
).

I suspect Power Apps is not ready for this functionality yet. Can be?. Any ideas?

Thanks in advance.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Linn Zaw Win 2,996 on at

Like (0)

Report

That functionality has been working fine and I have never experienced such an issue before. I just tested and I am able to see the records and select in the "Set Default Value" step.

The internal server error can only be troubleshooted by Microsoft Support engineers, so I recommend raising a ticket with them.

Meanwhile, you may update the lookup view of the LEGAL_ENTITY table by removing all the filter criteria to see if the lookup view shows all the data (so that you won't have to switch to a different view)

Was this reply helpful? Yes No
Verified answer

cantareroj 53 on at

Like (1)

Report

Dear,

after delete the custom table, and create it again, it works.
I guess the root issue was related with the changing of the name of the column which is the Primmary Name Column. From that action, many errors show up.

Thanks and apologies.

Was this reply helpful? Yes No
Jitendra_FT 72 on at

Like (0)

Report

Hi @cantareroj / @LinnZawWin

Is this solution working once deploy to downstream environment?

Though, it is possible to keep the lookup value GUIDs same across the environments but if the GUID values are not the same as development environment will this solution work in downstream environments?

Thanks for your time.
Jitendra

Was this reply helpful? Yes No