We have a situation, where the datatype of one of the schema attribute changed from string to array of string. The schema is not enabled for profile. We made the changes. But I see that the ingestion is still failing because of type mismatch. It's still seeing the schema attribute type to be string. Will I have to recreate the dataflow from scratch? I am not sure of the issue because we don't specify the attribute's datatype in the data mapping.
What if you add a new field in your schema for the array of string? So you have 2 fields: one that is the original one that is of string type, the other new one that is of array of string type. That also gives you the flexibility of sending data with either type.
What if you add a new field in your schema for the array of string? So you have 2 fields: one that is the original one that is of string type, the other new one that is of array of string type. That also gives you the flexibility of sending data with either type.
