Skip to main content

Hi everyone,

We’re preparing to import preliminary application data into LeanIX using Excel, but currently don’t have any External App IDs assigned to the applications.

Looking for best practices or recommended formats that have worked well for generating unique, consistent, and persistent External App IDs—especially during the initial import phase.

Any suggestions or examples from your experience would be greatly appreciated!

Thanks in advance!

Hi ​@RKBA 

I assume you want to have a human-readable ID field, which you can easily reference from other systems.

In this case, you can ask LeanIX Support to configure an auto-incrementing sequence field for you and specify the naming convention. Many companies use a prefix like APP plus a number, such as APP00001, APP00002 etc.


Hey great question, the auto-incremental externalId sequentially assigns the ID itself when a new factsheet is created. This means we have have helped customers standardize the IDs by prefixing factsheet acronyms ITC-01, IF-01, APP-01, etc during imports or creations. Chat with your Customer Success Manger or create a ticket and we can chat about the need to set up a middleware(e.g. Azure function, Lambda) to make this automated. As it is not directly out of the box, however we can provide guidelines on how to achieve this OOTB integration.


Hi ​@justinharclerode 

I’m not sure if I understand your post correctly. I am working with several companies where we configured auto-incrementing sequences without any external functionality like Azure Functions, Lambda etc.

Does this mean that you do not support auto-incrementing IDs anymore, (or only for those customers that already have them), and that new auto-incrementing IDs need to be implemented externally using Azure Functions or similar technologies?


Apologies I was working on another question. This can only be configured in the advanced configuration tab which is access to internal only usage for support. So this can be done without any external need. 


Reply