@rohit782192 when you build a macro, people often use dummy data or field names that could change. Selecting field mapping allows you to map incoming fields to those that exist in the dummy data that you use in the macro workflow itself when you set it up. For example:
In the following Filter, I have set this macro up using a dataset with a [Division] field.
However, someone else may come along with a similar dataset to use the macro, but the names may be different. In this example, lets just say they are using a field called [Region] instead of [Division]. In this instance, we would need to use field mapping to basically tell Alteryx: Anytime we have referenced the [Division] field, replace it with [Region] to facilitate the incoming dataset.
When you turn that on, you'll get prompted with a list of fields that are in the macro workflow. You can then select the incoming fields that should replace these from the dropdowns (you'll also notice the datatypes are displayed and restricted so that you can only map matching types):
Hope this helps to clear up mapping a bit but if you need any further explanation please let us know!
Hi @rohit782192 ,
This is used to do field mapping.
If selected, it allows application users to select appropriate fields and put them where needed. This is very useful when you have field names different from those embedded in the macro.
If this is not selected, there will be no option to do so.
In this case, if the macro is for example a standard macro without modification, there will be no field matching to perform and depending on how you have configured your macro, sometimes even no action to perform.
Attached are two screenshots with the first showing when it's selected and the second when it's not.
Is it clearer to you now?