In Output Filter, under Input, the record is empty, but in previous Transformation it is not

Integrator.io
1

Hi all. I'm new to Celigo, and am hoping this is an obvious solution. I've built a flow from ADP, I'm getting records back in Preview. Next I have a Transformation and I'm happy to see the Output record looking as I need it to. Next I have an Output Filter to filter out some records, but in the Input box the record is empty ( {} ), and nothing from it is available to filter on except one field I added in the Transformation. I'm wanting to filter by other fields.

The image shows an interface for defining an output filter, with a rule set to check if "record.FileNumber" is not empty, alongside an input panel displaying JSON data. (Captioned by AI)
The image shows an interface for defining an output filter, with a rule set to check if "record.FileNumber" is not empty, alongside an input panel displaying JSON data. (Captioned by AI)830×240 19.1 KB

Any ideas? Thanks in advance.

2

Hi @Michael_Krantz ,

Thanks for reaching out! We're aware of a similar issue and are working on resolving it. To confirm if the issues are the same, could you please share a screenshot of the transformation rules, making sure to mask any sensitive information?

As a workaround, you can copy the output from the Transformation window into the Input box record section. This will allow you to configure the filter.

We'll keep you updated once the issue is fixed. We appreciate your patience!

3

Thanks for your reply. I'll use the workaround -- thanks for that. The transformation rules just create 3 new fields:

The image shows a software interface for defining data transformation rules, specifying mappings for "FileNumber," "DeptNumber," and "GroupCode" from work assignment records with string types. (Captioned by AI)
The image shows a software interface for defining data transformation rules, specifying mappings for "FileNumber," "DeptNumber," and "GroupCode" from work assignment records with string types. (Captioned by AI)782×302 22.8 KB

1 Like
4

Thanks for sharing the details. This will get addressed as part of the issue we are currently working on. We'll keep you updated once it's resolved.

1 Like