Improvement suggestions, REST Object Type Connector

Hi,

Having experimented with REST Object Type Connector in a proof of concept situation expecting to use the module for production some time next year I have noted these things that would be beneficial as improvements:

1. Allow Column Mappings to use the same column for multiple purposes.
   A column's content may be needed both as ObjectID and as a property value.
2. Allow configuration of how the content is handled in Column Mapping.
   If the content is to be used in a lookup property you need to be able to specify whether to look for Name or ID of the lookup value.
   If the content comes in a different language or with different terms than used in a lookup property in M-Files you need to be able to translate or use ternary rules to produce valid output.
   Sometimes you need to extract only part of the content or to split the content and place part 1 in one property and part 2 in another property.
3. Set valid default values in Logging.
   The default values in Logging creates errors that prevent you from saving the configuration until you have changed the settings of Sensitive Data Protection and defined at least one target - even when you have logging disabled.

Items 1. and 2. of the above can be handled by placing the content in a temporary/hidden property and then use Extended Auto Properties to transfer the desired values to the final properties. So it is not a showstopper, just suggestions to make it a one step operation rather than depending on multiple follow up operations.
Most of the suggested features are already available in the HTTP Integration module.

Best regards,
Karl