Having strange behivor with On premises data gateway with SharePoint 2019, Is using the On premises Data Gateway fully supported with SharePoint 2019?

Question

Having strange behavior with On premises data gateway with SharePoint 2019, Is using the On premises Data Gateway fully supported with SharePoint 2019?

1- I have two SharePoint 2019 Farms and I installed On premises data gateway on one of the Farms.
2- I am using Azure Logic Apps to replicate data from one SharePoint document library in the first Farm to another SharePoint document library in the second Farm.
3- The strange thing is, I can do read and write operations -using logic apps- to the first Farm but for the second Farm I can not. I got Unauthorized error messages -see the below message from logic apps- although the user that I am using has the right permissions and I can do the read and write operations on SharePoint with this account using the browser.

{
"status": 401,
"message": "Unable to access the Folder in dataset https://xyz/sites/abcSite. Ensure that you have the right Permissions.\r\nclientRequestId: 2d0c07e4-9809-4b22-9e86-e4cc7f2bdbb1\r\nserviceRequestId: 367f8e9f-0141-8003-2dbd-67c5a282e854",
"source": "",
"errors": [
"-2147024891",
"System.UnauthorizedAccessException"
]
}

Appreciate your help.

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

I test with Copy File action, and it could only provide one connection in one action, so I think it does not support replicate data from one farm to another one.
If you have any update, please feel free to tell us.

---

If the response 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.