How to maintain technical name and business name for properties in Blueprint?

Blueprint and App Design
1

Hello,

While blueprinting data type, it could be interesting to be able to fix the technical rule property name intend to be created vs. the property Label.
For example, working on a Blueprint with business stakeholders in French, it is useful to work on data type and fields in French … but, when importing a Blueprint we do not want such french names for property rules … any idea how to manage this ?
I have an option to rework / fork the Blueprint (new release) before importing and updating all properties name … ouch, sound huge work event if I can ask the ai assistant to do it :slight_smile:

Anyway, it could be useful to be able (optional) to set the technical property name …

2

Hi @ColasM44 ,

I don’t think so, we can’t give two different names, i.e.., Label and ID Name.

image
image1759×570 37.1 KB

Thanks,
Ashok

3

Hi @ColasM44, thank you for your post.

While a separate Label and Property Name capability would be a useful enhancement in Blueprint, one option I leverage to today is to assign the field name for the desired technical property name and capture the business-facing French terminology in the Description field. This helps maintain implementation naming standards while preserving the business meaning within the Blueprint.