When adding new users accounts in AD and then subsequently to Sage System Admin/Sage 200 you will currently be asked to re-enter the credentials for the API user (as Sage ID).
The above is applicable to enabling the API externally
This is currently by design and works in this way to ensure the the Admin/API user is not removed unintentionally.
In particular scenarios site administrators my not require that additional challenge.
For example:
The API user may have left the business and the Sage ID/Password is not available or use of the API is no longer required .
In this scenario the previous API user would need to be removed and a new one to be set up following the documented process, the API could then be set up again if required.
This can take a short while and would require Business Partner and Sage support involvement.
Jimmy Beck
| Idea Benefit | A less intrusive check would save time and frustration for end users of System Admin , currently the challenge will show each time the application is opened. |
| How do you solve for this problem today? | Enter the Sage API users associated Sage ID |
| Product Variant | Sage 200 Professional (SPC), Sage 200 Professional |
