User Experience Insights
Establishing SAC Connection with SFDC
Recently, I was exploring SAC on SFDC for one of my clients.
While exploring I felt that the SAC – SFDC combination is not used much, as during my exploration I encountered multiple issues, which I had not faced when using SAC with other sources like BW4HANA or SQL Server or Standalone Excel upload.
Some of these were bugs, some by design, but as I mentioned I had not faced similar issue with other data sources, it was difficult to identify if the product was behaving wrong or I was not doing it the correct way. As a result, I had to turn to google to check if others have faced similar issues and to learn from their experience of resolving it, but even on Google or on SCN I could not find much…hence the above assumption that SAC – SFDC combination is not used much.
Therefore, I plan to share the same with all here as this might help others and/or hopefully give them some direction, if they encounter similar issue…this can turn out to be a multi-part blog series, as there were multiple issues we encountered, I will try to pen down the same as time permits.
Part 1 – Establishing SAC Connection with SFDC
- SAC connects with SFDC using the acquired connection also commonly known as Import connection
- The connection interface is common like for all other acquired connection.
- We selected Authentication type as ‘Basic Authentication’
- And entered the required details like Authorization URL, Username, Password and expected the connection to work…simple
- However, the connection did not work and gave out an error
- We cross-checked the details entered with relevant teams, but still the connection refused to work.
- However, the SFDC team, while sharing the connection details & credentials, had also shared one more detail and that was Secret key, but the SAC connection interface does not provide any field to enter secret key, nor does the help documentation mention it. Maybe SFDC’s local login interface provides a separate field to add the Secret key, but SAC’s does not. So there is no way to know If this piece of data is to be used at all, as none of us had earlier worked on SFDC
- As we were doing the trial and error, the basis team decided to use this piece of data somehow…but how was that data to be used, there was no field provided for it. Where were we to enter it, so the system can pick it up, if it really required it to establish the connection.
- In one such trial and error attempt, the basis team entered the password & secret key combination in the password field in a concatenated format i.e. Passwordsecretkey
- Success..It worked.
This is a minor issue, but when you are working on the new technology combination, with no help around in person or documentation and add to that a unclear interface with missing field, Minor issues become frustrating and time-consuming to resolve.
Hope this will save someone some time.
Thanks for Reading !!!