Introduction
In the article How to configure AFAS, you learned how to integrate AFAS with Workspace 365. However, you may run into some issues during configuration or experience issues with the AFAS live tile. Keep on reading to troubleshoot these issues.
OTP (activation) mail is not received
Explanation 1:
In the final step when configuring the AFAS App Connector, the users were not added to the Workspace App Connector group. And as a result, the OTP (activation) mail cannot arrive for the users, because they are not allowed to request this via the App Connector.
If you have access to the Workspace logs, you will see the following error. Note that the '12345' listed in the HTTP URL is an example, in your case it will be different.
NDAW.Afas.Exceptions.AfasException: Request 'https://12345.rest.afas.online/ProfitRestServices/otpvalidation' failed. Status code: NoContent
Solution:
Add the users to the Workspace App Connector Group by completing the final step under 'Configure AFAS App Connector' (step 1.10).
Explanation 2
Since Profit 16 the mail server was reset by AFAS. This could be a reason why the activation email is not being received.
Solution:
Configure the mail server in AFAS (click here for AFAS documentation).
Delete the OTP/verification code from the 'Configure AFAS App connector' screen.
Try again to configure the application.
"In order to activate AFAS, your account needs to have an email address (please contact your admin)"
Explanation:
This error message tells you that there is no email address to successfully do the activation flow. This applies to the admin, but also all users.
Admin: when clicking "Next" in the New AFAS connection dialog or when clicking on "Activate" in the AFAS live tile, and the account doesn't have an email address, it will show an error alert with the following text: "In order to activate AFAS, your account needs to have an email address".
User: when clicking "Activate" in the AFAS live tile, and the account doesn't have an email address, it will show an error alert with the following text: "In order to activate AFAS, your account needs to have an email address. Please contact your admin."
Solution:
Both the admin and users must have an email address configured in their user profile in Workspace 365 (also make sure that the admin is a user in AFAS as well, otherwise no mail is being send/delivered).
An issue with filling in the activation code ("your changes are not saved")
Explanation:
When setting up the AFAS connector in Workspace, you will have to fill in an activation code and you may receive the error “Your changes are not saved” despite the fact that everything seems to be configured correctly in AFAS.
If the AFAS connector has been changed in the meantime (prior to filling in the activation code), this will also change the ID connected to the AFAS connector. As a consequence, validation will fail.
If you have access to the Workspace logs, you will see the following warning:
Message:Failed to validate the Afas environment NDAW.WebApp.Common.AfasConfiguration.AfasConfigurationClientService+<ValidateConnectionAndRetrieveWebSiteUrlAsync>d__24.MoveNext(:0) (null) NDAW.Afas.Exceptions.AfasEnvironmentSetupException: Afas environment is not setup correctly. The GetConnector 'Workspace365_Tasks' is not available
Solution:
Recreate the connector in AFAS and try again.
Page not found (404)
Explanation:
When clicking on a task or signal from the AFAS live tile, we try to deep-link into the AFAS product. However, this is not always supported by AFAS. As a consequence, you see the 404 error message 'page not found'.
Solution:
To prevent this issue, edit the created AFAS connection in Workspace. Make sure you check the checkbox "Use default tasks URL when clicking tasks". Instead of navigating to the deep-link after clicking on a task from the live tile, you are now redirected to the overview page instead.
Cannot directly go from task in AFAS tile to the same task in AFAS InSite
From the AFAS tile in the workspace, you cannot directly go to the same task in AFAS InSite. This is not supported by AFAS.