Hi @ogonzalesdiaz ,
In Classic console UI, We can't directly edit in OOTB nms: recipient schema. So we are extending it, and giving different namespace to the extended schema. This is only in the UI. There won't be any new table named "abc: recipient" get created in the database.
But whatever you create delete or modify an attribute in abc: recipient, those attributes will be added or deleted in nms: recipient schema.
That's the reason you can see only nms: recipient in enrichment and not abc: recipient.
So to update the flag in your schema, after data loading, in update data activity you can configure as below:
Operation type: Update
Update dimension- nms: recipient
Records identification:
Select- using reconciliation key
Source: customer_cic(from file)
Destination: @codigointernocomputacional
Fields to update:
@flg_correo -- correo flag from file
@flg_sms -- sms flag from file