Answered

Intermittent Multiple Levels of many-to-one relationship expansion error

(0) Share

Report

Posted on by BrianPadgett

I am having issues where code that has executed with no problems now shows the dreaded "Multiple levels of many-to-one relationship expansion aren't supported" error message. My application stores information for 5 different types of forms or documents. For each document I use separate variables to store the data source record and the code is identical except for variable names and data source names. The error seems to arise intermittently among the different document types. For example, there are times when code documents 1 and 3 shows no error, but there are errors for documents 2,4 and 5. I have closed my browser session, cleared cache, and closed the Powerapps session. The next session it may occur that now the errors on document 1 no longer exist, but occur somewhere new. The error occurs even though multiple levels of expansion (beyond 2) isn't being conducted. I have included a very simple example below that illustrates the issue. vDoc and vFrm only exist for this example; they are not used within the application. SolutionChecklistGallery Items is a collection from the data source.

Set(vDoc, SolutionChecklistGallery.Selected);
Set(vFrm, vDoc.DRBForm);

Here is an image of the error.

This is causing issues where I can't use Filter, LookUp, or reference an object using syntax such as DataSource.Record.ColumnName.

What can be done to fix this issue? Any help is greatly appreciated.

Thanks,

Brian Padgett

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

v-jefferni on at

Like (0)

Report
Hi @BrianPadgett ,

In canvas we usually use AddColumns/DropColumns/ShowColumns functions to add relational information to the main table to create a template table by creating a collection.

ClearCollect(colTmp, DropColumns(AddColumns(ShowColumns(DataSource, "Column1", "Column2"),"ColumnA",ThisRecord.Column1,"ColumnB",ThisRecord.Column2), "Column1", "Column2"))

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

Was this reply helpful? Yes No
BrianPadgett 4 on at

Like (0)

Report

Just for any other community members who may come across this post. I opened a ticket with Microsoft. I have had multiple meetings providing information, exported the app, traced monitor session, and traced network activity. It was stated as a known issue. Since my original post, I have experienced opening the app in a new session and all the prior errors no longer exist. I have also spent hours commenting out code, saving, closing and reopening the app. Sometimes the errors are gone, most times they are not. When working with the MS break/fix tech, I showed him 10 pages that had errors. Without changing a thing, the next day they were gone.
I did not modify my code to AddColumns(DropColumns(ShowColumns(. I'll update the post if MS is able to provide a sustainable fix.
Thanks for the feedback.

Was this reply helpful? Yes No
HFG 516 on at

Like (0)

Report

@BrianPadgett

Did you ever get a solution to this ? My application which has been working fine for weeks is suddenly throwing this error on places where it is clearly not a multi level lookup. I can't even use the LookUp function because it won't retreive the value I need from the LookUp coumn to be able to use it in the function.

Help !

Thanks

Was this reply helpful? Yes No
ChrisBgt 23 on at

Like (1)

Report

This weired issue can still be observed ... when in app editing modus, a restart of the editor helped, the error vanishes.

Was this reply helpful? Yes No