workloadClient.itemCRUD.createItem error

[WilcoHendriksen]

I'm trying to get our workload to work in 'cloudmode'. The frontend starts the create dialog but when the 'createItem' function is called. I run into this error:

The payload that goes in, item here is DwhItem:

The error isn't very useful, so I was thinking maybe the nuget package is wrong, or the app registration.

I've uploaded this nuget package with this manifest:
BE/WorkloadManifest.xml

also the item was included.
Be/DwhItem.xml

The app registration:

The createItem never reaches our backend. When I call the backend in the browser, it responses with a 405 wrong method, because the service doesnt expect a GET request, but it reaches the backend. So that works.

https://%backend%.%domain%.com/api/fabric/workspaces/123/items/456/789

• CORS is allowed with all origin and all methods(just to test)
• idtyp optional claim is added
• All organizations is enabled

https://%backend%.%domain%.com/api/fabric/workspaces/123/items/456/789

What else can we do?

[anitamayorov]

Hi @WilcoHendriksen, do you see any network failures? If so, can you please attach a requestId of one of the failed requests for us to investigate it further? (/artifacts should be the correct network call)
If the error comes from the workload's frontend code, I suggest debug \ better log the info to be able to identify the root cause.

[WilcoHendriksen]

I managed to debug it a bit further and I noticed I have a duplicate workloadName somehow.

And there is a nice error thrown in "validateExtensionArtifactOperation" but that one does not get through.

Where does the system get the information from? Does it come from the nupkg or from %frontendurl%/manifests? Because I don't see double workloadId's in my package?

edit:
It seems we mixed up the item manifest which is used in localhost:60006/manifests and the one that goes into the nupkg. The item is transformed by the PublicToInternalTransformer.js they are different which you will only notice when you try thing in 'cloud mode'.

[anitamayorov]

Hi @WilcoHendriksen ,
In dev-mode using your local backend and your local frontend some of the information received from .nupkg (WorkloadName for instance) and some from the /manifests call (.json files that are going through the transformer).
Is your issue resolved now? If you still have issues with creating an item please elaborate and share requestIds, if exist.

[WilcoHendriksen]

I think I know how to resolve it. In 'Cloud mode' I need to remove the Org.workloadId. parts from FE/item.json then it should work.

Just to clearify a bit, in cloud mode it uses only the nupkg?

[anitamayorov]

Hi @WilcoHendriksen , yes, 'cloud mode' uses the .nupkg content only (assuming you don't have a running local frontend and your developer switch is off - otherwise it takes the local frontend /manifests code, that's the meaning of the developer switch)