9 Replies Latest reply on Apr 10, 2017 7:55 AM by Sanford Whiteman

    Inconsistencies in the way SFDC ID can be used?

    Grégoire Michel

      I observe an inconsistent behavior of the SFDC ID field:

      • It can be added to a view, displayed and exported
      • It can be used as a token in an asset


      • It cannot be used as a filter in a smart list...
      • It cannot be used as a token for the new value in a Change Data Value flow step
      • It cannot be used as the attribute in a "Data Value Changes" trigger not in a "Data Value Changed" filter


      Tested this on a couple of instances with the same result.


      Am I the only one to see this?