API user anonymization: how to included custom user fields
Hello,
I’m trying via Docebo connect to include Custom User Fields in the anonymization process. The example which can be found within Docebo connect works well with the standard fields but does not allow me to add the custom fields as a Data pill to the recipe. The part I’m struggling with the Child recipe where you need to define in the update user step which fields you want to anonymize. However it is not possible to select the Custom user fields.
I have created a custom action in order to retrieve all user data but then in this step I cannot refer to the “Filter to get users” neither to the page and the page size as is done within the standard step “update user”. Can somebody point me in the right direction please?
Page 1 / 1
Hey, I’ll link here to a previous comment of mine because it sounds (to me at least) like you need to update your schema somewhere to include the custom fields. Hope this helps!
Hello Ian, Thank you for your reply. I understand that I need to update my schema somewhere and preferably within my first GET users in Docebo action. In order for the additional fields to be available in the item list in the for each action.
In order to do so I have used a “Custom Action” which uses the GET method. This allows me to include in the response body all the user fields including the additional once. But in this GET method I seem not to be able to apply the filter as is possible within the standard GET User Action. as indicated in the screenshot below.
The custom action with GET method returns me all the users and all their fields but I only need a specific selection of users which is defined in the dynamic filter created in previous steps.
The question now is how do I get this filter applied to a custom action -method GET in order for me to continue only with those users that meet the requirements set within the filters.
Hi Wim,
If I understood correctly:
you have now created a custom action to get the users (GET manage/v1/user, I imagine), and
you updated the response schema for that custom action to include the additional fields you need, but
you have not been able to apply any filters to the custom action, as you would for the standard “Get users” action?
If that’s all correct, I think there’s an easy fix: filters are applied via Request URL parameters, so you need to update that part of the custom action:
You can also add the page and page_size here. Any and all of the parameters defined for this endpoint in the API Browser.
This should be all that’s required, unless I’m missing something here.
Hello Ian,
Thanks for the clarification. This was indeed the missing step. After some tweaking i got it working with the dynamic filters I required.
