on 10-31-2023 4:13 PM
The two apps from a new deployed project are not showing up in Work Zone content. After content refresh, the log shows:
{
"status": "PARTIAL",
"contents": {
"total": 8,
"failed": 3,
"status": "PARTIAL",
"messages": {
"aaa": {
"error": ["Failed to search aaa"],
"warning": []
},
"bbb": {
"error": ["Failed to search bbb"],
"warning": []
},
"AppHost_[object Object]": {
"error": ["Duplicate ID 'cc.spreadsheetimporter.v0_28_1' with version 0.0.1 found in application 'bbb' and repository id e5136b48-7e19-426c-806d-bc16247d5486"],
"warning": []
}
},
"correlationId": "0ae26385-5dfc-4bcd-73de-1eed26316690"
},
"reportId": {
"contextId": "SUB_ACCOUNT",
"subdomain": "application-sandbox",
"instanceId": "SAAS_APPROUTER_HTML5_APP_REPO",
"providerId": "saas_approuter",
"contextType": "sub_account",
"identityZoneId": "74c9d23b-b20a-4836-8f34-1dffda6c8e28"
},
"correlationId": "0ae26385-5dfc-4bcd-73de-1eed26316690",
"providerTitle": "HTML5 Apps",
"statusText": "Partial content was updated"
}
One error says duplicate ID found for spreadsheetimporter. I'm not sure if that is the root issue. Spreadsheet importer is used in both apps.
The deployment works fine on my trial account that has "standard" Work Zone but fails on company system with "standard" Work Zone. Both systems have other apps already deployed before the new package. Is there a difference between the trial "standard" WZ and regular "standard" WZ?
Thank you for any guidance.
We use it on premise in only one app for the moment which works fine. This doesn’t help you but what I’ve noticed is that you configure it as a dependency and it will be deployed as a sub-component inside the component where you use it.
In theory it should work fine as long as you have only one component that uses it but as soon as you have multiple it will deploy it multiple times.
My suggestion would be to deploy it as a separate component instead of configuring it as a dependency. Connect it using the namespace and let WorkZone resolve the dependency. This approach will require you to manually get the spreadsheet importer component from GitHub to deploy it to btp.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
c3d1947136cd4c748a7aa794001af496 jayjohnson14
Thanks Wouter for you suggestions.
I havent worked with a lot with Workzone yet. I tried to recreate it with a new project but did not run into the error you described.
In the CAP folder i have two Fiori Elements App with Spreadsheet Importer and used the "Decentralized deployment" described in the documentation. Then deployed the mtar and used it in Workzone.
Can you share more information about your setup and project?
I described the "Central Deployment" in the documentation, but more detailed for ABAP. If you can share more information for how to work with Workzone, you more then welcome to share it so i can document it for others.
Hi c3d1947136cd4c748a7aa794001af496 thanks for your reply, it's given us a lot to think about. Would you mind clarifying the process of connecting an app to the component using the namespace? Or do you happen to have a link to some documentation or other resource that describes this process? Thanks again 🙂
maybe this can help in case it is deployed in the same space: https://blogs.sap.com/2023/11/09/connecting-ui5-components-in-btp-cloudfoundry-in-the-same-space/
or when in different spaces: https://blogs.sap.com/2023/11/09/connecting-ui5-components-in-btp-cloudfoundry-across-spaces/
Thanks c3d1947136cd4c748a7aa794001af496, I just saw that you had published this series of blog posts just in time for this issue. 🙂 Appreciate the help!
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.