When a column of a Business Object is configured as Localized, and then this configuration is undone, the extended BO related to the primary one does not delete the reference to the translated columns.
We can consider it as a bug of the product, but there is a workaround that solves the issue. This article will use the "Status_fr" column of the CI business object, but can be useful for any similar error.
This error only occurs when accessing the application in a language other than English. In this case, the error showed to the user was: "Erreur d'accès aux données : Invalid column name 'Status_fr'.."
This workaround is a way for cleaning the references to the translation column. The screenshots are related to French, so the field you will see is “Status_fr” of the CI business object, that would be “Status_de” in German, etc.
Please follow these steps:
6. Check the CI top level tab, it should be working properly
NOTE: This article was writen for the field "Status_fr" of the CI table, but it is possible to find the table where the field is using the following SQL statement (please modify the FIELD_NAME):
o.name AS TableName,
c.name AS ColumnName,
o.type AS ObjectType,
u.name AS SchemaName
FROM syscolumns c
INNER JOIN sysobjects o
inner join sysusers u
ON u.uid= o.uid
c.name like '%FIELD_NAME%'