Create new folder action in SharePoint Connectors is not working through the on premises gateway against SharePoint 2019 on premises, Is it a limitation?

Question

Firstly, Create new folder action in SharePoint Connectors is not working through the on premises gateway to against SharePoint 2019 on premises, Is it a limitation?
I am getting the below message when I tried to create new folder in a SharePoint 2019 document library through the On premises data gateway. I am wondering is it a limitation and why. Is it exceeding the payload limit

"Message": "This operation is not supported when using this with the On-Premises Data Gateway.

Secondly, I know about the payload limits when using On premises data gateway, but why copy file action is not working while using "Allow Chunking" option.
Allow chunking should be a great option with this limitation but why it's not working.

lastly, Why Microsoft documentation is not clear about the SharePoint Connector actions limitations

Answer 1

@Mohammad Amer Discussed with the core team and we will be documenting the details soon. For now I am sharing the list of supported features :

OnPrem SP 2013 and 2016
Here are the connector operations that should still work. Anything not listed is unsupported.

Triggers:
• When a file is created in a folder
• When a file is created or modified in a folder
• When an item is created (Note: Does not support “Limit Columns by View”)
• When an item is created or modified (Note: Does not support “Limit Columns by View”)

Actions:
• Get file metadata
• Get file metadata using path
• Get folder metadata
• Get folder metadata using path
• Get file content
• Create file
• Update file
• Delete file
• Copy file (deprecated) (Note: this is the one with “deprecated” in its display name. It is NOT the same as “Copy file”)
• List folder
• Extract folder
• Get attachments
• Add attachment
• Delete attachment
• Get items (Note: only supports OData params. Does NOT support any new parameters such as “Limit Entries to Folder”, “Include Nested Items”, and “Limit Columns by View”)
• Get item (Note: Does not support “Limit Columns by View”)
• Create item (Note: Does not support “Limit Columns by View”)
• Update item (Note: Does not support “Limit Columns by View”)
• Delete item
• Send an HTTP request to SharePoint

OnPrem SP 2019
Some additional operations are supported. Again, anything else not listed is not supported.

(Supports everything in the 2013 / 2016 list above)

New triggers/actions supported:
• When a file is created (properties only) (Note: Does not support “Limit Columns by View”)
• When a file is created or modified (properties only) (Note: Does not support “Limit Columns by View”)
• When an item is deleted (See *DeletedTriggerNote)
• When a file is deleted (See *DeletedTriggerNote)
• Resolve Person
• Set content approval status

Updated triggers/actions. These actions have changed “under the hood” and should be more reliable than they used to be:
• When an item is created (Note: Does not support “Limit Columns by View”)
• When an item is created or modified (Note: Does not support “Limit Columns by View”)
• Get items (Note: only supports OData params. Does NOT support any new parameters such as “Limit Entries to Folder”, “Include Nested Items”, and “Limit Columns by View”)
• Get item (Note: Does not support “Limit Columns by View”)
• Create item (Note: Does not support “Limit Columns by View”)
• Update item (Note: Does not support “Limit Columns by View”)
• Delete item

Obsolete. These triggers/actions are considered “obsolete” and we discourage customers from using them:
• When a file is created in a folder (use the “(properties only)” one instead)
• When a file is created or modified in a folder (use the “(properties only)” one instead)

*DeletedTriggerNote
While the deleted item trigger is supported in this OnPrem version, it is missing a number of fixes that happened more recently, so the experience might not be optimal. Specifically, I can see these problems:
• If there is no activity on the list for over 60 days, the trigger will just start failing
• If there no items deleted for over 60 days (but there could be other activity) in the list, then the trigger will just start failing
• Items deleted by the System User will not be skipped

If this helps please "accept the answer" and " up -vote" so that it could help others in the community.

Answer 2

These are known issues/limitations in On-Premises Data Gateway working with SharePoint Server 2019.
You can check the Community section under Error Details for related posts on this error.

The document can be outdated and not specific in writing about the known issues and limitations. I would suggest you submit your feedback via the Feedback section on the bottom of the document.
You can either submit a feedback for this product or for the mentioned document to help Microsoft improve the documentations or the On-Premises Data Gateway.

Thank you for your understanding.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
**Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. **