Missing attachment name when app is created in SAP BAS

SAP-samples / abap-platform-fiori-feature-showcase

Feature showcase that demonstrates and documents how to implement annotation-driven SAP Fiori Elements UI features for oData V4, using the ABAP RESTful Application Programming Model (RAP).

Apache License 2.0

131 stars 31 forks source link

Missing attachment name when app is created in SAP BAS #14

Open rammelbalagtas opened 1 week ago

rammelbalagtas commented 1 week ago

I noticed the attachment function is working perfect from ADT but when app is created in SAP BAS, the attachment name is not showing even after I have selected a file. As you can see below, the draft is updated after I selected a file but the filename is not being shown.

I have a posted a similar question but nobody has replied me yet. https://community.sap.com/t5/technology-q-a/the-upload-file-name-is-missing-in-object-page-when-fiori-app-is-created-in/qaq-p/13735041

skeuker commented 6 days ago

Would like to comment that I've stumbled accross the same issue. We have developed an App that works correctly in ADT Preview but once deployed to SAP BTP Workzone Launchpad the table line item does NOT visualize the fact that a file was just uploaded. Even though the ADT Preview and Work Zone Launchpad use the same UI5 version the behaviour is different. Would appreciate a fix to Fiori Elements such it also behaves correctly from SAP BTP Work Zone Launchpad.

RupertNold commented 6 days ago

I can confirm this behavior, I have the same problem. At the first upload the attachment name is not displayed. After a manual refresh in the internet browser everything is fine. In ADT preview it is working correctly, but in the deployed Fiori Elements App not any more.

jessie-cheah commented 1 day ago

Thank you to Stefan for opening a ticket. The Fiori Elements colleagues are working on a fix for this issue but in the meantime, they are suggesting the following workaround if you need a resolution immediately:

You have defined your pages with a property called "contextPath", like:

"contextPath" : "/SalesOrder"

I guess you used SAP Fiori tools to generate the application or the pages (which is for sure the right approach).

contextPath is the replacement of the entitySet as this is more flexible, but caused an issue while introducing.

Instead of the contextPath, you can use entitySet, with the entitySet mentioned here, so instead of:

"/SalesOrder" just "SalesOrder", or "/SalesOrder/Item" just "SalesOrderItem".

I'll keep this issue open until the actual fix from FE is available