This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 30%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFJ%3C/text%3E%3C/svg%3E)
Since a few weeks ago, after updating the AddIn node in the App Registration we use, we have seen a change that has quite an impact on our developments:
The "client" parameter that arrived at the endpoint before was "SharePoint" in submissions from SharePoint Online and Teams, and "OneDrive" in submissions from OneDrive.
What has changed so that now the value "OneDrive" arrives from SharePoint Online, and how can we solve this problem? We need your feedback on this.
Thanks in advance.
Best regards,
Fernando
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 33%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXX%3C/text%3E%3C/svg%3E)
Hi, To better help you reproduce & test your issue, can you elaborate on the update steps you went through?What are the results now?
Yes, of course.
We have an App Registration for File Handler 2.0 connectivity. In the "AddIns" node of the manifest we have four "custom" actions that point to our own endpoints.
Until the update, our endpoints, through the HTTP POST made by the App Registration through File Handler 2.0, received in the "Client" property of the "ActivationParameters" the value "SharePoint" when the origin (client) was SharePoint Online or Microsoft Teams channels, and the value "OneDrive" when the origin (client) was OneDrive for Business.
After updating the "AddIns" node to include two additional "custom" actions, we get the "Client" property of the "ActivationParameters" the value "SharePoint" only from Microsoft Teams channels, and the value "OneDrive" when the origin is SharePoint Online or OneDrive for Business.
The strange thing is that this behaviour does not happen in all updates. There are tenants in which it is happening and tenants in which it is not. We do not know what the casuistry is and why. We know that Microsoft is making updates, as the appearance of the File Handler 2.0 menus has changed and now appears in a unified way in SharePoint Online and OneDrive, and we suspect that this problem is derived from the update they are doing.
Hi, After my internal and external searches, there is no official documentation on this phenomenon. Regarding the inconsistent behavior observed across different tenants, it's possible that these changes have been rolled out progressively. As a result, some tenants may have received the update while others have not, leading to the discrepancies you've noted. You can do a waiting period if this does'nt affects your business, which should be universal for all users.
OK, but the answer does not give me a solution to the problem. I want to know in which cases this situation occurs in order to be able to make decisions and propose solutions.
Does this affect File Handlers 2.0?
This change talks about migration of SharePoint Add-Ins, but does not indicate anything about File Handlers 2.0: https://learn.microsoft.com/es-es/sharepoint/dev/sp-add-ins-modernize/sp-add-in-modernize
In this update, the new SharePoint menus appear (expanded and with icons) but there is no mention of File Handler 2.0 either, although it does affect its visualisation: https://techcommunity.microsoft.com/blog/onedriveblog/the-enhanced-edit-in-grid-experience-for-document-libraries/4373895
Can you investigate and tell us something?
@Xyza Xue_MSFT , is there any progress on this?