API need to be exposed on the Swagger for use
N
Nikhil Pant
In the previous version of Enate, we utilized the following API to update the DataDictionary field, which functioned as intended –
However, following the upgrade on the UAT instance, this API is no longer operational as it is classified as an internal API.
We require this API to update the Datafields. Within GroupM, we have datafields such as VendorList and PubzonDetails that necessitate frequent updates.
The process is outlined as follows -
- GroupM users input the pub details and vendors into SharePoint.
- A separate process retrieves the most recent list from SharePoint and synchronizes it with the database table.
- Ultimately, the UiPath process accesses the list from the database table and updates the Enate list. For any invoice processing on Enate, these lists must include the updated items added to SharePoint.
Kamal Saran
Hi Nikhil Pant,
Thanks for the detailed write-up — really helpful. Just to confirm, after the UAT upgrade the
DataDictionaryField/Update
endpoint is no longer usable because it’s now treated as an internal API and it’s not exposed in Swagger, correct? If you can also share which Enate version your UAT is currently on (and any error/response you’re seeing when calling the endpoint), that will help us investigate.We’ll review this on our side and come back to you once we have an update.
N
Nikhil Pant
If this cannot be exposed as the external API, we will need an alternate API to update Datafield.