Can you provide a sample text/Json or screenshot  of  value(in CIT log/debug). I can check in old notes if some mapping script can do the trick.

Thank you, Misaq. I had to shift to address other priorities, and am only now finally able to revisit this.

I am querying using Connect-It MaaS connector 9.91 against SMAX 24.4, a custom entity called Software_c. One of the fields in parameters I ask for is of ENUM_SET type, and in the example record, has two values:


The Connect-It debug does show the connector successfully querying and returning the data:

"Filling node data from http response ... "

...but in the mapping result, an empty string:

I was thinking for GetListITem or ItemCount from old function but then again this is a new connector. Out of the box ENUM maps well but if you create custom enum I think it may run into same issue. There has to be an internal function that gets the value of it. As same ENUM SET is used for "Data Domains" . Unfortunately my test instance is prepping for DEMO so I cant touch it.

I will do some testing on generic JSON ENUM data and see if it can pull some values.

Do you get anything in from with your PifLogInfoMsg ?   

One another way would be to introduce custom function for getting the attribute but that would impact scenario performance if its a large data extract.

Forgot to mention this one. Should try and see if source  has some parsed data

PifXMLDump - Connect-It

Thank you, Misaq, I believe you are on the right track.

I noticed that using PifXmlDump it does not include the ENUM_SET field (node) element in the output.

I also tried a test simple scenario without using custom entity, just used Article built-in entity and DataDomains built-in ENUM_SET field, to see if the fact that I was using a custom entity was relevant. It did not include the value for Article.DataDomains either.

So, I believe the MaaS connector has something internal that does not process ENUM_SET into usable xml data by mapping, and simply omits it, despite the Java debug showing that the ENUM_SET is being returned as an array of data values successfully in JSON from SMAX.

I am going to open a support case to report it and see if they can confirm/re-create as a potential issue with the MaaS connector.