Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Nicole Jünger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Feature Setting Name: Matching Criterion

  • Feature Name: Dynamic Pricing

  • Value: Is for you to configure. Please use the following syntax and don't forget the squared brackets to close in the whole string, and curly brackets for each value, separate everything with a comma

    Code Block
    [{"operator":"==","field":"API Name of Field from Campaign Item (or related object)","conditionField":"API Name of the Field from Price Rule"}]

Above is in the screenshot you can see an example of custom matching criteria for the billing category field located on Ad Price level.
Another example is the combination of multiple fields, such as matching criteria for a custom Start and End Date:

Code Block
[{"operator":"<=","field":"ADvendio__until_Date__c","conditionField":"Custom_End_Date__c"},{"operator":">=","field":"ADvendio__from_Date__c","conditionField":"Custom_Start_Date__c"}]
Info

  • Please make sure that you use no whitespace or linebreak in the setting

  • You can use any field from an object related to Campaign Item, to do the objects need to be connected via Lookup / Master Detail Field and you need to enter the whole field path.

  • Any of the following operators can be used: ==, !=, <, >, <=, >= Attention: not all operators can be used for all field combinations, example < will not work when comparing Picklist Fields or Checkboxes

  • To reduce errors, make sure the fields you compare are of the same type, and picklists have the same picklistvaluespicklist values