when to use sqlname atribute in schema definition

[Shrutii]

@Parvesh_Parmar ,@AkshayAnand 

,@isahore ,@AndreaBriceno,@ParthaSarathy

,@ParthaS ,@Craig_Thonis ,@Manoj_Kumar_ ,@Amine_Abedour ,@Marcel_Szimonisz,@DavidKangni 

,@Amit_Kumar,@ShashankNigam02,@Ganesh5067, @Jonathon_wodnicki

@Amine_Abedour 

Hi All,

I have observed that  sqlname="loyaltyid " is mentioned in schema definition for attributes in schema 

may i know why so

normally in my old experience we have not defined  sqlname="loyaltyid " n schema definition for attributes in schema definition

why we need to define sqlname="loyaltyid" in schema definition and when<attribute desc="loyaltyid" label="loyaltyid" name="loyaltyid"
notNull="false" sqlname="loyalty" type="long"/>

[ParthaSarathy · Accepted solution]

Hi @Shrutii ,

By default, sqlname will get auto-genarated. Example, for attribute name="loyaltyId" of long data type, sqlname will get auto generated as iLoyaltyId (you can see this sqlname for all attributes in preview tab).

Instead of iLoyaltyId, if you want to use different sqlname, you can define sqlname="loyalty"