Hi everyone,
I’m facing an issue when executing an action that uses "Excel To Record List". I’m getting the following error:
OS-BERT-60500 - Error executing actionAmbiguous binding of the '' column header; prefix it with the entity name and a colon (':').Ambiguous binding of the '' column header; prefix it with the entity name and a colon (':').Ambiguous binding of the '' column header; prefix it with the entity name and a colon (':').Ambiguous binding of the '' column header; prefix it with the entity name and a colon (':').
Here’s what I’ve checked so far:
The Structure used in the conversion correctly matches all headers from the Excel file.
The same "Convert from Excel" (with different structures for different files) works fine in other actions.
The same action works in Test and Prod, but only fails in Dev.
I tried replacing the Excel files and even used the exact same ones that work in other environments, but the issue persists.
Here a screen of the structure and the file headers:
Has anyone experienced this issue before or has any suggestion on how to solve it?
Thanks in advance!ODC Studio version 1.5.33
Hi @Giovanni Piccirilli ,
Have you checked any blank spaces in header name?
sometimes blank spaces cause this type of issue.
Regards,
Manish Jawla
Hi, sorry fort the late response.Yes i've checked the headers and also downloaded and used the same Production file.I've also deleted the action and recreated with the same code as i've done it with the structure but nothing changed.Thanks
If it works in Test/Prod but fails only in Dev, here’s what usually happens in OutSystems:
Excel import is case-insensitive and environment caches header mappings differently.
In Dev, the structure definitions or Excel header parsing may be slightly different (for example, because of BOM, hidden spaces, or a different version of the Excel file). Columns like data, name, code are too generic and sometimes clash with reserved words or internal mappings. In Test/Prod the metadata may have cached one mapping, but in Dev OutSystems can’t decide which attribute to bind → hence the ambiguous binding error.
So even though the same file works elsewhere, Dev is stricter because:
The Excel file uploaded in Dev could contain invisible characters in the header row (space at the end, UTF-8 BOM, etc.).
Just to confirm: If you download the same Excel that works in Prod and upload it directly in Dev, does it still fail? If yes, then it’s 100% a Dev structure metadata / reserved word conflict, not the file.
Hi there and thanks for the detailed explanation.Yes, i've downloaded the production file but it fails in DEV env.On your suggestion I'll try to change the excel headers to different values and so change the structure definitionThanks