QuestionQ209

VerifiedOrchestrator and Automation Cloud

An Action App is created by using a Data Service entity with two fields: Name (string) and Age (number). After the app is published, the entity schema is modified—the Age field changes from a number to a required string field. Existing users continue using the earlier published version of the app.

What is the most likely result when a process that expects the updated schema is triggered?

Explanation

A numeric Age value from the earlier app contract does not meet the updated requirement for a required string Age field. The process therefore encounters schema/type validation failure rather than automatically converting the value or ignoring the change. UiPath Data Service identifies field type as part of entity schema and documents that customized field types cannot be changed after creation, reflecting the incompatibility of such a type change.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!