@William-- @MarvinRhode - I've encountered the same problem and wonder if there's a solution. The link provided appears to be no longer working or has been removed!

@lgaertner Thanks a lot! This clears the doubt! 

I just stumbled upon this - Could anyone tell me what Fusion's *concepts* mean?

@William-- Any update on your response above? I am unable to view your response

@William-- Thanks for your answer, unfortunately, I cannot view your answer. Could you share the link once again?

Hello Venkat @Jvenkat , I appreciate your prompt and comprehensive reply. Currently, we're using Sharepoint and it requires us to refresh the token regularly. In Fusion, this is straightforward because we have modules set up with Client Secrets that create a new authentication token for SharePoint w...

Considering the current limitation of manual token refresh, what steps can be taken to mitigate the associated risks and improve the efficiency of the authentication process? Currently, we have to do a manual refresh of the token used for authentication. There is no direct way to automatically updat...

Considering the current limitation of manual token refresh, what steps can be taken to mitigate the associated risks and improve the efficiency of the authentication process? Currently, we have to do a manual refresh of the token used for authentication. There is no direct way to automatically updat...

Thanks a lot for your detailed response. Will explore a little more on what you just mentioned above!

The plus sign (+) is a URL encoding replacement for a white space. In the context of URLs, it represents a space character. However, SharePoint APIs expect spaces in field names to be replaced with, not a plus sign (+). This is likely why you're getting a 400 error - the URL is not recognized due to...