I've been testing the scripted connector after attending Empower 2024 and noticed that while some JSON files work fine, others do not. The issue seems to occur with nested JSON files containing very little data. I haven't been able to pinpoint the cause of the failures.
Could anyone advise where I can check the logs to identify what's going wrong? Unfortunately, I can't share the JSON example as it contains sensitive data.
Thanks.
As this question has now been inactive for a long time, I will close it. If you still want more information about this, could you post a new question?
Hi Lucas,
Thank you for attending Empower. It's great to see that you are continuing with Data API and scripted connectors!
Data API is provided by a DxM with the same name, and scripted connectors are executed by the DxM DataAggregator. For troubleshooting, I suggest you check the log files of these DxMs. You can find DxM logging at C:\ProgramData\Skyline Communications.
If you are using DaaS, you won't be able to access the log files because you need file access to the server. We know about this issue and are working on a solution.
You can also make the HTTP request to the Data API directly to get error messages. There is a swagger file available on the server at http://localhost:34567/swagger/index.html, but this also requires direct access to the server.
If you are using DaaS, you can run your HTTP call from an automation script and print out the error message.
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer that has been most helpful for you (using the ✓ icon)?