IXP Generative - Data - Extractor - Updates

I am using IXP generative Extraction.

This creates Extraction Results with an Extractor type such as “GptIxp83”.

Variables are then created in the code to pass the data to Action Center, as well as look at the response from Action Center.

Code flow works, until the Extractor Model is enhanced, perhaps a minor change to the prompt to get a better result. (i.e GptIxp85)

Now the Code breaks - The Extractor reference has changed and no longer matches the variables in the code.

Can anybody provide some advice how relationship between IXP extractors and code is actually suppose to work?

Yes, the Document Extraction use the “Live” tag, but that does not flow into the other structures in the code.

Hopefully somebody has a practical approach to this challenge?

Regards, Dave

As an example of the error encountered in code:

Argument ‘CreatedValidationAction’: BC30311: Value of type ‘CreatedValidationAction(Of GptIxp83)’ cannot be converted to ‘CreatedValidationAction(Of GptIxp68)’. The selected value is incompatible with the property type.

When the “Create Validation Task” and “Wait for validation task and Resume” are added into worklfow the Extractor is getting set and then cannot be amended.

The activity needs to be deleted and re-created.

This feels like a serious UiPath BUG - has anybody else encountered it?

Hi,

In this case, it may be better to use older style DU workflow. Because it separately handles IXP model and extraction results in workflow. If IXP model changes, we can address it by changing the field mapping.

Regards,

Hi @Yoichi

Thanks for the suggestion but that is missing the benefits of the IXP Generative approach.

If there are changes to the fields being extracted I could understand why code changes might be necessary. However, when there are IXP changes to the prompts which results in “better” values being placed into the existing fields, I can see no logic for justifying code changes.

Regards, Dave

Hi,

I agree what you mentioned. Unfortunately, I think there are currently no means to achieve that. It may be better to have a version-independent super class.

Regards,

1 Like