Flow Designer: Invalid data pill provided in Action for field even if mapping a Password (2 Way Encrypted) in the same typeDescriptionFlow Designer: Invalid data pill provided in Action for field even if mapping a Password (2 Way Encrypted) in the same typeSteps to Reproduce 1. Create a custom field 'password2' in the sys_user table with with type=Password (2 Way Encrypted) 2. Create a custom table [u_custom] extended from taskAdd a field 'Second password' referencing the custom field sys_user.password2 you created in step 1 3. Create a Flow 'Test passwords' which will trigger upon creation of record in [u_custom] table 4. Create a custom action'Password 2 action'Inputs - password and type=Password (2 Way Encrypted) 5. Add this action in the Flow 'Test passwords' Mapped the password2 field in the password input eg password=Trigger > Custom Table trigger > Second password > password2 Actual: Flow Designer:Invalid data pill provided in Action for fieldExpected: It should map correctly since they are both Password (2 Way Encrypted)WorkaroundNOTE: Property comes as read only. Please raise a support request for further assistance. 1. Go to sys_properties2. Find com.glide.hub.flow.enable_validation and set this to false3. Run cache.do, i.e. go to <instance>.service-now.com/cache.do or enter "cache.do" in the navigator to refresh the instance and have the new property value take effect4. Add the password2 pill onto the field5. Save the flow. This will now work. With the property from step 2 turned off, we will receive a warning now instead of an error6. When you are done working with this flow, turn the validation property back to true and run cache.do again to refreshThis property is useful for a situation like this because we know that the mapping is correct You can temporarily turn off the validation. You can also choose to leave the property as false. Validations will still run, but saves will not be prevented and any errors are presented as warnings instead. Related Problem: PRB1498885