How do you get field mapping in workflow actions working?

The feedback from ​@sagili (I think) was:

Seems like an issue with the workflow builder failing to render static schema, I will check and update.
For now you can use remote schema (and return the same structure)

I’ve done that, but the results were unexpected:

👉 Is it for example possible to map a date field in Outlook to only date columns in monday?

Like so:

👉 Can I map a person in Outlook to only people columns in monday?

I’m also finding that all fields are required, even when they are marked as nullable

An example:

{
  ...
  location: {
    title: 'Location', // Label shown to the user
    type: 'primitive', // Type - primitive or custom
    primitiveType: 'string', // Used only for primitive fields - string, number, boolean, or date
    isNullable: true, // use true if the user can leave the field blank
    isArray: false // use true if user can choose multiple options
  },
  ...
}

👉 How do we set fields to be optional in the workflow UI?

I have more learnings on remote schema, workflow builder UI & the input for custom actions (see image).

It seems that workflow builder allows you to add any column into a field and the column text value is sent over to the action. This is very limiting, because you then need to validate and interpret the data.

For example if it passes a date/time column, this gives the date/time text in the workflow owner's local format and local timezone, which really means very little. I need the complete date/time in UTC in ISO8601 format really to target the exact date without having to then work out & correctly parse the exact start time. THis will allow me to work with dates across timezones.

Is there a way to just get the column IDs rather than just the text values? -- That way, it's easier to just go and get the correct data

Some other points:

• all fields are marked as required, even if you specify `isNullable: false` in the remote mapping.
• you cannot specify which column type you need - e.g. only I’d like to be able to select only columns of type date, or only columns of type people
• you cannot select just the column - you need to select the column dataa subtype - say for column of type person, I'd like to get all the data
• The values from columns of type date are returned in the local date format for the integration owner - I need the complete date/time in UTC in ISO8601 format really to target the exact date without having to then work out & correctly parse the exact start time

Also, it allows you to populate each field with multiple columns. How can this be prevented?

Interestingly, the native workflow action to create an Outlook event will allow any column type and data into the Invitees field without any complaints:
 

I’d have expected this to behave a little better, so now I’m not sure what to think. 🤔

that seems like a bit too much to expect from end users to figure out what they should map to what.

Another advantage of field mapping if it worked correctly would be that you could select columns subitems. This could be incredibly powerful if it worked better.

With the normal fields, you can only select items (based on their type) from the main board, not the subitems board:

With field mapping, you can select columns from subitems...

...but, allowing end users to select columns of any type is really opening up a big bag of worms for supporting this.

How do you specify only the types of columns that should be allowed in this dropdown?

In this example, only columns of type date should be displayed.

For comparison, this is what is shown in the sentence builder when mapping columns - only columns of the correct type are shown in each field:

Cc: ​@sagili ​@OmerK 

Just nudging this topic again. 😉