cancel
Showing results for 
Search instead for 
Did you mean: 

FIORI Elements List Report Text in edit/draft mode

pmcfarling
Participant

Cannot seem to figure out how to display the text from @ObjectModel.text.element:['textName'] when in draft/edit mode. The key is a UUID and very ugly. We've tried setting the textInEditModeSource property to "NavigationProperty" via controller extension ( using VSCode/FIORI Tools). Even loaded the application in WebIDE and setting it there using the UI5 Visual Editor but no luck.

gregorw
Active Contributor
0 Kudos

Hi Paul, Hi vinod.snair ,

I think I face the same issue. I've filed the incident:

393237 / 2021 UUID shown in edit/draft mode

with detailed instructions how you can replicate the issue with my sample CAp app bookshop-demo. I have a V4:

http://localhost:4004/webapp/fiori-latest.html#V4UsersUI5latest-manage

and a V2:

http://localhost:4004/webapp/fiori-latest.html#UsersUI5latest-manage

to replicate the issue.

Best regards
Gregor

View Entire Topic
marcmaurí
Participant

Hi pmcfarling and gregorw ,

I was struggling with value lists last week and I got really weird behaviors.

Gregor, I don't know if it would be the best option, but in your sample you can solve it by adding the following annotation:

annotate AdminService.Employee with {
 ID
 @Common.Text: { $value:email, @UI.TextArrangement: #TextOnly };
}

Then, in edit mode you got: (see attachment)

Note that in that case, #TextOnly / #TextLast /... produces the same result (I guess it is due to the Hidden annotation of the ID property).

Best regards,

Marc

gregorw
Active Contributor
0 Kudos

Thank you Marc. That works great in V2 and also V4. Now only the issue exists that V4 doesn't update the other fields when a new Employee is selected. V2 does.

marcmaurí
Participant

Hi gregorw ,

as I got from the FE Tools team in the beta program, the implemented side effects in V2 and V4 are not equivalent.

For the V4 you need to add the following side effect annotation:

annotate AdminService.Users with @(  
  Common.SideEffects #employeeChange : {
    SourceProperties : [employee_ID],
    TargetEntities   : [employee]
  }
);

Best regards,

Marc

gregorw
Active Contributor
0 Kudos

Hi Marc,

thank you for sharing. Works like a charm. Is that already documented

Best regards
Gregor