when to use sqlname atribute in schema definition | Community
Skip to main content
S
Shrutii
Level 4
March 6, 2024
Solved

when to use sqlname atribute in schema definition

  • March 6, 2024
  • 1 reply
  • 496 views

@Parvesh_Parmar ,@AkshayAnand 

,@isahore ,@AndreaBriceno,@ParthaSarathy

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"/>

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ParthaSarathy

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"

 

1 reply

ParthaSarathy
Community Advisor
ParthaSarathyCommunity AdvisorAccepted solution
Community Advisor
March 6, 2024

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"

 

~  ParthaSarathy S~  Click here to join ADOBE CAMPAIGN USER GROUP for Quarterly In-person | Hybrid | Virtual Meetups
    Terms & ConditionsAccessibility statement

    Loading footer...