Problematic "Unnamed Object" in Fiori Elements app powered by RAP endpoint

[DouglasCezar]

Hello dear colleagues,

I have a scenario where I expose data from a table using RAP. Some fields that are part of the table key can be empty. For such fields, they look good on the OData V4 provided, they come empty as expected.

The problem is: we created a Fiori Elements app on top of this OData service, and when we look at the resulting table, all fields that should be displayed empty have the text "Unnamed Object" on them. This happens in multiple fields in multiple rows.

The columns in red are all part of the table key (and they are allowed to be empty), while the column in green is not part of the table key. So only the columns used in the table key display the unwanted "Unnamed Object" text when empty.

If you have any ideas or insights, it will be more than appreciated.

Thanks a lot!
Kind regards.

[Marian_Zeis]

By desgin a key is not allowed to be empty, so you may need to set the keys to other fields or create a UUID for the entries as single key field

[KjetilKilhavn]

Two possible causes come to mind, but I am just speculating here since I haven't tested how this would behave.

• The table underlying the data you have exposed is not defined with the "Inital Values" flag. Therefore your data have NULL values
• Your data model have defined these as foreign keys, and the foreign key check table (e.g. T001W for your Plant field) doesn't have an entry with the initial value

Remember: The more information you provide, the better answers you get. You have provided very little information here, so the quality of the answers reflect that. 

[MioYasutake]

@DouglasCezar 

Alternatively, you can use the i18n extension to overwrite the default "Unmanaged Object" text.

https://sapui5.hana.ondemand.com/#/topic/63946c02df1d45efbbad5b1658fef3a5