How does "Enforce mandatory fields" work on transform maps?

[edwin_munoz]

Hello everyone,

I was expecting that by selecting this option the records that have empty values for the mandatory fields were going to be ignored but I'm still getting records with empty values on the mandatory fields.

Does anyone knows how this option works?

Thank you

[bernyalvarado · Accepted solution]

Hi Edwin,

Enforce Mandatory Script has 3 options:

a) No

b) Only Mapped Fields -- which only validates the fields been mapped

c) All Fields - which validates all the mandatory fields of the target table.

Whenever the transform fails due to this trigger it will show something like the following:

"field_name, other_field_name" are mandatory fields

I'm guessing that perhaps your transform didn't work because of one of the following reasons:

a) your mandatory field is not mapped and your enforcing the mandatory fields to only those mapped

b) your input values are not been interpreted as empty/null but instead as a string with a space or something like that.

To validate that correctness of this function I went to my OOB developer instance and confirmed that it's working as expected. They way i validate it was by:

1) setting a couple of fields in the sys_user table as mandatory

2) setting the user transform map to enforce mandatory fields based on all fields

3) generating a record in the imp_user table with the missing mandatory fields

4) and then i got the transform error for each record with the message: "first_name, user_name" are mandatory fields

I hope this helps sir!

Thanks,

Berny

[edwin_munoz]

Thanks Berny,

I think it may be because empty values may have a space or something, I'll check what's happening and reply back.

Thanks

[Jitendra Namdev]

How did You made the field mandatory , via DATA policy ,  UI policy , Form designer or client script. Also if you did via UI policy or Form designer then for which view ?