@fa__ with i-doit OPEN version 29, Add-on are not longer supported For version i-doit OPEN 28 and below, you can find the old api download files in the Knowledge Base here: https://kb.i-doit.com/en/download-links.html#api-add-on i-doit Add-on API 1.15 Required i-doit >= 27 i-doit Add-on API 1.14.1 Required i-doit >= 24 i-doit Add-on API 1.14 Required i-doit >= 1.19 i-doit Add-on API 1.13.1 Required i-doit >= 1.19 i-doit Add-on API 1.13 Required i-doit >= 1.19 i-doit Add-on API 1.12.3 Required i-doit >= 1.15

@fa__ it is not possible to modify entries. Editing entries would not be audit-proof. @StefanP74, looks like there are more and more bot answers that work with ai models.

Hey @fa__, there is acutally no validation for these Attributes in the API. A feature feedback exists.

Thank @Michael-Overkamp! I confirm that the hotfix solves the issue.

Hello @fa__, yes there is a XML Export available. [image: 1662024231096-a3bc52b7-568b-4f18-9d6f-03be8f99d3a1-image.png]

Hi @philipp-hörselmann, Yes, I was using the ID of the license object. It works fine with the license entry ID. Thank you!

Thanks @michael-overkamp! I had not undestood that multiselect is a Dialog+, I thought it was a different kind of attribute.

In this topic, it is explained how to manage tags using the API. The limitations in the use of tags I mention in my previous post do not exist. However, I am still wondering about the consequences of using tags vs object groups.

Hey @fa__ yes, that's correct - working with the ID will work, since i-doit does not have to "look up" the correct version on its own. I have created a bug ticket for the this Thanks for finding this issue! Best regards Leo

Thanks @michael-overkamp! It works fine.

Thank you @lfischer . That solved the issue, now the API returns the password decrypted.

@michael-overkamp It works fine now. Thank you!