Please Share your Product Ideas with us!

All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.

Add <EMPTY> to the list of available values in the value mapping drop down.

Often it is only after initial field mapping is done where the field has been set to an xRef do you find that it is necessary to value map a specific value to an Empty field.
Currently there is then a need to change the field mapping to a Rule Xref and add the code.  This is additional work which is not productive.

  • Tim Empson
  • Jun 13 2018
  • Unlikely to Implement
  • Attach files
  • Admin
    Andy Lund commented
    7 Nov, 2019 02:55pm

    HI Tim - if you have a Source Value that should not be mapped, the Not Relevant flag can be used. This will indicate that the mapping is complete and resulting mapping will be a blank field.

  • Tim Empson commented
    29 Aug, 2018 07:16am

    Correct Jon.  I would like an option to always be able to map an existing value to <EMPTY> or <BLANK>

    This is not available to us - so we have to then change the rule mapping from an xref to a rule xref.

    Sorry for the delay - vacation.

  • Admin
    Jon Green commented
    24 Aug, 2018 10:39am

    Tim could you clarify this a little further.  Do you mean that you want a target value of <EMPTY> always available to map to or a source value, or am I misreading this?