Not getting correct JSON response

[jernejp]

Hi,

I'm building an app that has a custom connector. This is the response I was supposed to get:

But when I trigger my request like this:

Set(
    AddActivity;
    'MyCustomConnector'.AddActivitiesToBusinessPartner( { params })
)

The AddActivity variable looks like this:

I also tested the connector and got the correct responses.

So my question is - does anyone understand, why I can get the correct response when I test the connector in the backend, but not when I trigger the request from within my application?

[v-xida-msft]

Hi @jernejp ,

Based on issue that you mentioned, I think you have some misunderstanding with the data storage representation within PowerApps app.

According to the correct response you mentioned (last screenshot), I think the dll property owns a Object value. When you executes your action within a canvas app, the Object value the dll property returned would be recognized as a Record type. Then within the variable, the dll property would be rendered as below ("table" icon):

you could click the "Table" icon as above to see the detail values within the dll property.

Actually, it is a normal behavior that the Object record would be redered as a "Table" icon as above when your variable or Collection contains a Object value.

If you want to reference the column values within the dll property, please take a try with the following formula:

AddActivity.dll.retval

AddActivity.dll.BUSSINESPARTNER

AddActivity.dll.EMPLOYEE

AddActivity.dll.SUBJECT

AddActivity.dll.LOCATION

AddActivity.dll.STARTDATE

...

Note: The AddActivity represents the variable you set in your app.

Currently, within PowerApps, only simple type column value could be displayed within a variable or Collection directly (e.g. the status property in your response), the complex type (Object, Array, ...) column would be rendered as "Table" icon as above.

Best regards,

[v-xida-msft]

Duplicated

[seadude]

Hi @jernejp , also try searching the forums here for "nested JSON". There is a plethora of examples that solve exactly what you're looking for.

Good luck!

[jernejp · Accepted solution]

What solved the issue was when I deleted the connection to my custom connector and made a new one. Looks like it was still using the "old" version, ever though I've updated the connector.

[jernejp]

Thanks to everyone for your replies, really appreciate it!

[v-xida-msft]

Hi @jernejp ,

Have you solved your problem?

If you have solved your problem, please go ahead to click "Accept as Solution" to identify this thread has been solved.

Best regards,