Since we have turned On the "New analysis engine" setting, our app is having issues around data population in Collections.
For example, My Dataverse Table 'A' has columns 1,2,3&4 (Column 2 is Choice Yes/No) and when initialising a collection, Collect(colTest, Filter(A, 2 = '2(A)'.Yes)) but the collection 'colTest' does not show any data for columns 3 and 4. The data only appears for column 1 and column 2 (which is in unsupported format).
"New analysis engine" setting, causing issues with data population in Collections
Update your formula to use ShowColumns() to explicitly specify the required fields: Collect(
colTest,
ShowColumns(
Filter(A, 'Column 2' = '2 (A)'.Yes),
"Column 1",
"Column 2",
"Column 3",
"Column 4"
)
)
The new engine may require explicit handling of choice fields. Use the .Value property to refer to the actual value of the choice field: Collect(
colTest,
Filter(A, 'Column 2'.Value = 'Yes')
)
To isolate the issue, test the Collect function without applying any filters: Collect(
colTest,
ShowColumns(A, "Column 1", "Column 2", "Column 3", "Column 4")
)
All columns used in filtering and collection have compatible data types. Any relationships or lookups are properly expanded (e.g., using AsType for polymorphic lookups).
Was this reply helpful?YesNo
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.