Skip to Content

Dump error when opening UI Designer
There could be multiple reasons for dump, following are few among them :

  1. UI inconsistency due to multiple changes from different users, we have observed multiple times different users try to make changes for the same screen /field /button. That will create duplicate change transactions (CT ) and result in inconsistencies.
  2. Perform save and activate once the changes are done from your end.
  3. Perform Metadata update to avoid inconsistency.

Button comes up as disabled on screen
Make sure enable property is true in UI Designer .
Unable to use extensibility framework on a SAP delivered Button/Button group/Section group / List / Tabs . 

  1. Anchor is not provided by SAP application team for partners to enhance UI element like – Button/Button group/Section group/ List / Tabs .
  2. You can create an incident with valid business use case to provide the anchor on UI element like – Button/Button group/Section group/ List / Tabs .

Issues related to change in Mandatory / Read only property using Adjust Property in Extensibility explorer.
PDI: Adjust Property in Extensibility Explorer :

“OR” operation is followed by mandatory and read-only property.

Example: If one CT with READ-ONLY property is “TRUE” then the field will always remain READ-ONLY as true irrespective of any other CT on that field.
You need to delete extra CT created under Adjust Property modeler. Follow the steps:

  1. Get the control id of the field/button/ UI entity (for which Mandatory/Read-Only property is having issue) from UI designer -> Properties.
  2. Open the extensibility explorer. Select the anchor for which changes are applied using Adjust property modeler.
  3. Get the extra CT created under Adjust property by checking the xml of CT for that particular control id for Mandatory/Read-Only property.
  4. Delete the CT which is making the Mandatory/Read-Only property as fallback value = true.

Issues related to change in Visible / Enable property using Adjust Property in Extensibility explorer.

“AND” operation is followed by Visible and Enable property.Example: If one CT with Visible property is “FALSE” then the field’s VISIBILITY will always remain FALSE irrespective of any number of CT on that field.
You need to delete extra CT created under Adjust Property modeler. Follow the steps:

  1. Get the control id of the field/button/ UI entity (for which visible/enable property is having issue) from UI designer -> Properties.
  2. Open the extensibility explorer. Select the anchor for which changes are applied using Adjust property modeler.
  3. Get the extra CT created under Adjust property by checking the xml of CT for that particular control id for visible/enable property .
  4. Delete the CT which is making the visible/enable property as fallback value = false.

Error while solution deployment
If such error occurs and there are red dots on any component under that particular solution in Cloud Studio then it means Solution has inactive contents.

Activate all those components (with red dots on it) separately and then finally activate the solution.

RBAM authorization error for partner created UI. (Not on partner extended UIs) 
There could be multiple reasons for dump, following are few among them :
First of all, update your Cloud Studio to latest version.
Now follow the steps:

  1. Find the UI component where such RBAM issue is occurring.
  2. Open the solution in studio.
  3. Find the Partner BO on top of which this UI component was built.
  4. Check for the UI components with extension .TT or .uiwocview built on top of that BO. Open those UI components in UI designer.
  5. Check under properties for ShortID of that UI component.
  6. Complete ShortID text should be in upper case as per RBAM policy guidance.
  7. If the ShortID has any character in lower case then you need to delete that UI component and recreate using Create screen wizard on top of the BO. This time it will create the UI component with ShortID completely in upper case.
  8. If the original UI created was using the option – “Select Screen” to create screens individually then you should create the new screen using same way.
  9. But, If the original UI created was using options other than “Select Screen” to create a set of screens with navigation then you should create the new screen using same way using that same navigation option but before that you need to delete all other UI components built along with that affected UI component on top of that Partner BO because this option creates all set of UI along with referencing each other components used for navigation.[ All those UI components having same short ID as the affected UI component needs to be deleted ]

Unable to delete Partner created UI in Cloud Studio due to reference from other UI components/PDI Anchor.
When a screen is created by selecting navigation scenario in Cloud Studio, a set of UI components are created based on the selected navigation. All the UI components are referenced by one another. For deleting such UI components, you need to delete them from top to bottom level reference approach. This is because all the child level UI components will have a reference in it’s parent UI component.

For example: OWL will have a reference in WCVIEW which in turn will be referred by Work Center (WCF). Try deleting in this order:

WCF, WCVIEW, OWL, QC, QV, TI, TT
In case, WCF is referred by any PDI anchor then first this PDI anchor or the reference needs to be removed then follow above steps.



Issues where Partner needs to generate load of UI component
Example scenario: Partner created UI using ByD Studio which is built on Partner delivered BO. At a later point of time, Partner edited the BO by changing labels and tooltips and then activated it. This change got reflected in UI Designer but it didn’t came on frontend UI. The reason for this issue is UI Load.
Load Invalidation :-

This feature was introduced in UI designer for manually triggering Load invalidation by Partners. It’s a button in UI designer.

UI load can only be generated in XREP and partners don’t have access to backend. So this feature is introduced for manual invalidation of Load as only option which can be used by Partners to Invalidate the load. Now, By simply clicking on Load Invalidation Button or using it from Tools Menu, Partner can Invalidate load on XREP at any point of time. If any issue like this comes, it can be resolved by Load Invalidation

New Button to open QC is not visible.
This could be issue with authorization, role of the user or ThingType name in case components are created via PDI
Partner/User can check following points:

  1. ThingType, Quick Create, Thing Inspector, Quick View should be part of AssignedObjects of WorkCenter View and user should have authorization for this WoC View.
  2. User should have valid role for editing /creating new data via QC.
  3. If these components are created via PDI, please make a point that Short ID of Thing Type is case sensitive and it should be in upper case and same at all places, for eg: in Inport of QC.Please check in all components and confirm the case also of ThingType.

Feature not available in other devices like Mobile / Tablet .
Perform tagging for the particular device from extensibility explore UI designer for the UI to be available in required device.

Add Extension Field to Section Group not available in Extensibility explorer.
Please check the anchor modelling for particular field group , Add Extension Field to Section Group will only be available for Extension Anchor.

Example scenario you can find in below link:

Link : https://blogs.sap.com/2016/05/25/add-extension-field-to-section-group-missing-in-the-extensibility-explorer-of-ui-designer-sdk/

 

 

Query missing in the frontend.
You should defined an anchor for the query defined in the UI Designer .
Example scenario you can find in below link:

Link : https://blogs.sap.com/2016/05/25/option-missing-to-personalized-query-in-the-frontend/

 

How to define basic search option using SADL query. 
Please refer to the case document – 2338075 – How to define Basic search option using SADL query

How to define Custom Modelled Queries or SADL Queries in UI Designer for filter option.
Please refer to the case document – 2333980 – How to define Custom Modelled Queries or SADL Queries in UI Designer for filter option

 

Help Content on SAP Cloud Application Studio and UI Designer
SAP Cloud Applications Studio – SAP Help Portal Page

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. SAMUELE BARZAGHI

    Thank you!

    These links to support.wdf.sap.corp, not public?

    How to define basic search option using SADL query. 
    Please refer to the case document – 2338075 – How to define Basic search option using SADL query

    How to define Custom Modelled Queries or SADL Queries in UI Designer for filter option.
    Please refer to the case document – 2333980 – How to define Custom Modelled Queries or SADL Queries in UI Designer for filter option

    Sam

    (0) 
  2. Deepty Mohnani Post author

    Hello Sam,

     

    These are case documents and it is released for customer.

    You should be able to access these documents. Please try again and let me know if still you face any issue.

    Thanks & Regards,

    Deepty Mohnani

     

     

     

    (0) 

Leave a Reply