ServiceDataParser macro for 2023.2

[deepakvasu]

Hi, Does ServiceDataParser macro continue to work with 2023.2 or is there another method to extract readable information from outputlog on AS_RESULTS to see status of completed scheduled jobs/error message? Thanks.

[fmvizcaino]

Hi @deepakvasu ,

The service data column was removed from MongoDB on version 23.2 and replaced by a set of new columns + the output log binary column.

Since I don`t have access to this version, I have never tried, but I believe it is only a matter of converting the binary column to a blob and then output as a file. You can accomplish this by using the blob convert + blob output tool. Maybe I`m missing something here but maybe other people will be able to contribute to my answer.

Best,

Fernando Vizcaino

[venza]

Hello,

I tested every blob conversion option in the blob conversion tool without success.

So no, the blob convert tool doesn't work.

[patrick_digan]

@deepakvasu @venza The Service Data Parser continues to work for me in 23.2. I grabbed the outputlog from the AS_Results table and used the attached macro to convert the blob data to text.

[deepakvasu]

Thank you for above responses.

The blob convert/output route does not seem to result in a readable file/string? With blob convert route, I did convert outputlog to hex, then removed spaces and other characters (I'll explain why in a moment) and then converted hex to ascii (string). However, the content of outputlog seems long and detailed and I am looking to identify the summary outcome error message(s) which I could not locate in this string. As a result examining the string and going back to hex codes, the outputlog content seems to be truncated (comparing to message output from corresponding workflow on gallery). Hence I could not locate error message this route.

Trying to apply dataserviceparser (thank you for copy of macro) in the input step it makes reference to a file we don't have then in the next step gives question mark with content below:

[patrick_digan]

@deepakvasu Can you share a screenshot of the info you're looking for from the gallery? 

For that question mark, it does look funny but it should work. It's just pointing to some internal alteryx components. Was the macro throwing some sort of an error? I will say that if you've already parsed the data manually, the parser will be doing the same thing. So that route sounds dead anyway.