Recently active topics

En muchos proyectos de Arquitectura Empresarial aparece, antes o después, la necesidad de agrupar aplicaciones y capacidades por dominios (por ejemplo, Customer, Finance, Supply Chain, HR, etc.).Sin embargo, LeanIX no ofrece actualmente una estructura clara out of the box para modelar dominios como tal, y he visto enfoques muy distintos según la organización: uso de tags o convenciones de naming subtypes o campos custom reutilización de otras entidades (con mayor o menor encaje) o directamente decidir no modelarlos  Me gustaría abrir el debate y conocer vuestras experiencias: ¿Usáis dominios en vuestra implementación de LeanIX? ¿Para qué casos de uso concretos os resultan útiles? ¿Cómo los habéis implementado y qué dificultades habéis encontrado? ¿Creéis que es un concepto necesario o prescindible? Creo que compartir experiencias aquí puede ayudarnos a evitar tanto el over-modeling como quedarnos cortos en la estructura.

Is anyone tinkering with the MCP server? It seems to be missing fairly basic functionality like retrieving all the fact sheets of a given type. It has an action to get all applications, or to search for fact sheets of a given type, but the search doesn’t support a wildcard, so there appears to be no way to get a list of fact sheets of a given type. Has anyone run into this?Thanks -Dan

Users who were previously assigned to specific access entities in LeanIX had these entities removed from their accounts. As a result, their access to the corresponding factsheets was revoked.

Is there a table that shows a list of default fields for each fact sheet and fact sheet subtype? I’m working on migrating from Meta Model 3 to Meta Model 4. However, I don’t know what I should expect for some of the new sub types in Meta Model 4, such as the following new sub types:Business Context Fact Sheet SubtypesBusiness Product Customer Journey Process Value StreamInitiatives Fact Sheet SubtypesIdea Program Project EpicI would assume that if a customer purchased LeanIX today that each new subtype would come with prebuilt fields specifically tailored to each subtype.  For example, Business Product and Customer Journey under the Business Context would have different fields. I’ve followed the steps to rename old Fact Sheets (E.G. From projects to initiatives) and created the SubTypes, but I would expect a list of default configuration/fields for each subtype instead of trying to create them from scratch.  I’ve searched the community and documentation but can’t find a good resource. 

Hello Team,We are mapping Business capabilities in Lean IX and we are doing our best to keep it to Standard.As part of that i am not able to find appropriate Business capability for Inter and Intra company or for an Internal Procurement.Also i am not fully getting how to define Application, System and System Component. We have SAP S/4 Hana and we use all the Modules. Any leads would be highly appriciated

I'm confused about the relationship between Application Lifecycle and Business Capability dates in LeanIX.When I fill out an Application fact sheet, I can already specify the Lifecycle status (Plan, Phase In, Active, Phase Out, End of Life). However, when I map that same application to a Business Capability, the system asks me to enter 'Active From' and 'Active Until' dates again.For example, if a customer uses SAP and has already filled in the Application Lifecycle, why do I need to specify these dates again at the Business Capability level? What's the purpose of having both, and what's the difference between them? The distinction isn't clear to me 

Junte-se a nós para um webcast especial onde apresentaremos as últimas novidades do SAP LeanIX.Quando: 17 de Dezembro - 10:00 BRNosso time de especialistas demonstrará de forma prática como as novas funcionalidades podem ser integradas aos seus processos do dia a dia, potencializando ainda mais o uso do SAP LeanIX em sua organização. Teremos também a participação especial de um cliente, que compartilhará como utiliza esses recursos em sua empresa.Registre-se aqui 👈🏻

Hello LeanIX community:I’m in the need for detailed documentation or example scripts for use in Automation to update subscriptions in one factsheet with the subscriptions in another factsheet.  I have already gone through the LeanIX Documentation for Automations and Automations with Scripts, and have not found the information I need.  Especially with the latter, the examples of scripts, as the examples in the documentation do not fit my case and there’s not enough detailed information on the syntax of the script code to generate different scripts for other uses.I would like to generate a script for use in an Automation that would for any Application factsheets that have changed (for example Application Location field) will Set Subscription for a New Subscriber equal to User with an existing Subscription from the IT Component factsheet (with a relationship to the Application factsheet) where Subscription Type is equal to Responsible and Subscription Roles equal to the value of “Service

How on earth do you get the interfaces map to work?It is frustrating me to high heavens, and I am ready to cal it quits with the entire LeanIX MESS. I have active interfaces. I have Active provider applications. I have Active Consume Interfaces.Why on earth is there still a message about missing data?What is this Circle Map report looking at in order for it to include “inventory”.Whilst on the topic, shouldn’t it give a more descriptive set of data, or a “true” create from scratch reporting tool to get at least operational data out of the application? Help, please. 

We have a couple of custom LeanIX roles set up in our organization, facilitated via SSO.  One of these roles is associated with the majority of employees in our company, we’ll call it “RO” for short, and another is associated with the team of individuals responsible for updating these diagrams (we’ll call it "RW”).  If I set the baseline permissions of a diagram to read-only, I haven’t been able to find a way to assign Read/Write permissions to members of the RW role.  It looks like the only way to assign these is at the user level for every diagram we have published.  The end goal is to have a sort of “diagram reference library” which, when published to, is read-only visible to the larger role group without having to manually grant write permissions to the smaller individually, per user, per diagram.Is anyone doing this today? 

 Application Fact Sheet I see Life Cycle with ANY. When is Fact Sheet classified as ANY?And I see NA, if the Lifecycle fields are not filled. Correct?

How to model Power Apps applications in LeanIX as they are huge in number and might consume license numbers but these applications are used locally which supports single capabilities?

Hi All, we have LeanIX for a few months now. We tend to work with managers for their respective areas especially around applications on a quarterly basis. We are integrated with ServiceNow for Application data primarily. I am interested to know what you do to ensure your data is maintained and how do you approach overall data accuracy/completeness. Thanks!

I need assistance with creating/updating users in SAP LeanIX. As the application administrator, I can only perform this individually. Does anyone have a step-by-step guide on how to do this?#LeanIX ​@DenisSouzaSAP 

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!

We're thrilled to continue with our Best Practice Webinar series titled "Architecting the Future: The Five Layers of Clarity." This is the final session in an insightful five-part series designed to provide you with essential strategies for enhancing clarity in Enterprise Architecture.Join Transformation Success Manager, Mobin Barati for our latest Best Practice Webinar series “Architecting the Future: The Five Layers of Clarity,” that follows the transformation journey of a fictional healthcare company, InnoSphere Health Solutions, as it builds an enterprise architecture practice from the ground up.🗓 Date: Thursday 11/12/2025🕒 Time: 11am AEST (Brisbane)📍 Online: Register hereIn the last session we learned how to expose critical gaps in data ownership and trust. In this session, we will delve deeper into the technology architecture layer of the Meta Model. We will answer:How to de-risk your foundation with technology architecture insights?Whether you're an experienced architect or n

Hello Everyone, I am quite new on LeanIX and I have some basic questions particularly Technology Architecture. I would like to create a Tehcnology Application/Solutions Buildng Blocks, ABB-SBB catalogue on LeanIX, but there is no ready excel file for that. Where should I start?In addition, I need to create Roadmap report for each and every SBB.Could lifecycle information be enough for IT components, but what about for physical data centres or cloud subscriptions? Should I also create them as IT components with their contract lifetimes? 

Hi all, Trying to filter for all interfaces for a specific application as a provider “OR” as a consumer. This option is not available in the filter. Thank you.Best Regards, Hugo Gomes  

Hi,We are writing Solution documentation in Confluence and are embedding LeanIX diagrams. In this documentation we describe different customer accounts with different adoption of e.g. Applications.One view in LeanIX we use a lot in LeanIX diagrams is the Application - “Fields on Relations” - Organization Usage or Ownership.Having set which customer accounts are using which application (in LeanIX) we see this diagram coloring up correctly…. BUT!I want to store that view with e.g. the name of the account but without storing the diagram itself. Otherwise I will get a lot of diagram copies and when the original diagram changes it will cause problems of course.Is it possible to save a view and refer to ONE diagram to avoid this? Or any other solution 

Hi everyone,Starting your SAP LeanIX journey is an exciting step toward effective Enterprise Architecture (EA) management. However, before diving into the tool, the single most critical step to ensure a smooth, successful, and impactful onboarding is to form your core team.  Why a core team is essential The core team is the engine of your LeanIX adoption. Their primary goal is to drive the vision, ensure value realization, and maintain the platform's integrity. They keep the scope tight, drive adoption, and are responsible for reporting the measurable Return on Investment (ROI) of your LeanIX implementation. The core team will be responsible for completing the SAP LeanIX onboarding process, a vital step that positions them to effectively cascade knowledge and drive adoption among relevant stakeholders within the organization.  Without this dedicated group, adoption can stall, data quality can drop, and the value of your EA effort may never be fully realized.  How to form your core team

Hi, we would like to set some automation to inform users about a Fact sheet is long time in broken seal status. How to get this information? Is this possible at all, maybe with graphql query?In addition would be nice to have a dashboard to make this information visible (which factsheet is since when in QS broken for example)thx for all the advice!

It is hard to believe that the end of the year is quickly approaching. It feels like our Q1 What's New Webinar was yesterday, but alas it is Q4 and the final webinar of the year will be on December 9th! You can find the registration page here.I will be accompanied by the familiar faces of Hunter Kislauskis, Ricauter Urdaneta, Seth Lippincott who will be reviewing the below topics:Enhance Rationalization decision making by managing TCO Meta model additions Notify the right people at the right time Automations on string fields & Numeric Fields Conditions including Lifecycle & Numeric fields Dynamic Email Recipients Govern your AI Journey AI Agent Hub  If you can't join us, have a happy holiday season, and we look forward to collaborating with you in 2026!