Forum Discussion
I finally got a response back from SnapLogic support and, in my opinion, it isn’t ideal. In order for an API Only user to view executions of all pipelines via the Public API, that user must be an organization administrator. Giving the API Only user access to individual project spaces or directories doesn’t do anything.
Another fun tidbit, there is no way to view who is an organization administrator in the UI. Apparently, it can be done using the public API, but, in my experience, it didn’t return who was or wasn’t an org admin. Must be something only SnapLogic admins have access to.
@dmiller if this is incorrect in any way, please let me know, but this is my understanding.
I’m double checking with Engineering and Product Management on the first point.
And true, only org admins can see who are in the admin group within the UI. Would you want to see who were admins?
- philliperamos6 years agoContributor
That sounds good.
I pivoted the data using as JSON, and then used a combo of JSON Splitter/Mapper and Data Validator to validate the data. I still had to hard code some JSON generation scripts, but that was the easy part.
Thanks!
- Ksivagurunathan6 years agoContributor
the way we developed, we don’t need to make changes to the snaplogic pipeline if we want to validate different set of files. it could be new set of validation or few new column validation to the same set of files. all we need to do is add validation rule to the table and corresponding file name. its more dynamic validation of data and column name in a file
- philliperamos6 years agoContributor
Thanks. We’re thinking of doing something similar for the dynamic validation approach, as the way I described above is leading to huge memory problems.