The multi-part identifier could not be bound error

[zcapkova (Zuzana Čapková)]

Was there any change in the resolving of data structures, joins etc.? After updating to build 2021.1.0.2248 (might have happened earlier) I get the following error when I open a previously working screen.

A 420 error is thrown for the MasterRecord and RowStates services, but the screen is loaded and the column causing the error is filled.

"Error loading data from table 'DataTransPayment' into entity 'DataTransPayment'
Message: The multi-part identifier \"CustomerGroup.Name\" could not be bound. 
Exception was encountered while updating data. For more information see Details."

[washi (Petr Hrehorovsky)]

There was a change related to resolving of data structure SQL commands - SQL generation for lookup fields with filters on joined entities by washibana · Pull Request #264 · origam/origam-source · GitHub.

[zcapkova (Zuzana Čapková)]

Lookup field is rendered incorrectly by server and architect

A lookup field is rendered without the “lookup” part in the name of the field. Data structure > Filter > Actions > Show SQL [image] Server log 2021-10-15 11:14:40,685 [10] ERROR Origam.DA.Service.DataLoader - The multi-part identifier "CustomerGroup.Name" could not be bound., SQL: SELECT [DataTransPayment].[DataTransReturnLocation] AS [DataTransReturnLocation], [DataTransPayment].[RecordUpdated] AS [RecordUpdated], [DataTransPayment].[RecordCreated] AS [RecordCreated], [DataTransPayment].[I…

[washi (Petr Hrehorovsky)]

Solution is discussed in Limits on SQL generation of lookup fields.