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?
Hello Lucas,
I have been working extensively on creating elements using a connector and/or Automation Scripts. So far, I have been using the IDms class. Here is a short example:
IDms dms = engine.GetDms();
IDma agent = dms.GetAgents().FirstOrDefault();
DmsElementId id = agent.CreateElement();
To check the logs for errors, you can use the information event console inside Cube. There is a good chance you will find valuable information about any errors you might encounter.
I hope this answer was useful to you. If not, I apologize for any misunderstanding.
Hi, to clarify: the question is about the Scripted Connectors which is a Python, or PowerShell script that is automatically running every minute to retrieve data and then push this to the Data API, which is going to automatically create a connector and element and will fill it with data. The solution provided in your answer is about an automation script, which is something different. More info about scripted connectors can be found here: https://docs.dataminer.services/user-guide/Advanced_Modules/Data_Sources/Data_Sources.html
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)?