Checking managed object using 'asset properties' (cockpit) vs. using postman - discrepancies

Forum
1

Hello,

some fragments are seen in postman but not seen in asset properties in cockpit

example: in postman:

image

while in asset properties in cockpit, it is not showing

image
image717Ă—286 12.4 KB

what is the difference between both? both fetch the data from MongoDB correct?

2

Hi GII

Just a guess: maybe the space between “…_Electrician” and “Helper” is causing problems.

greets

Helmut

3

no the problem is not in the spaces, it seems at a first glance that the “extract property“ doesn’t handle sequences as values, it works well for simpler structures like integer or strings. I had to implement the option of an HTML widget as a workaround. But for sure HTML widget using an API call may be a little bit heavier than “extract property“ widget so hoping that extract property current issue would be fixed to handle this type of data:
“list_of_workers_Zone6_B2_Electrician Helper”: [

    "DEEPAK CHAUDHARY VASU CHAUDHARY"

],
4

any cumulocity expert advice about the symptom we are seeing?

5

Hi GII

I can reproduce this on my tenant. I think this is wanted behaviour. Asset Properties are key-values. If you create a fragment with an array, this is like a key with multiple values. The widget don´t know which of this values to display. I think that´s why it is not shown in properties configuration.

Why do you need to use an array?

6

Hi GII,

Currently asset properties widget does not support array. We want to support this and we do have it in our backlog. We will make it available in our future releases.

2 Likes