• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 5692 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Schema extension vs custom property fields

acoromi
over 8 years ago

Hi all.

We are facing the need to use some more fields than the "standard" ones for the Employee information. We are unsure if it's better to extend the schema of the Person table, or use the "custompropertyxx" fields.

Initially, we think that schema extension will permit us to have fields with consistent names, and thus, it will improve the readability of the implementation. But we are asking at the same time, if it could be a problem when we will do any upgrade to the product.

 

Thanks.

  • 0 over 8 years ago

    Hi,

    The custompropertyxx fields are there for you to use freely - you can change the caption(s)/templates etc. of the fields but you can't change the datatypes. So if they work for you I would encourage you to use them. Any changes you make (via Designer) are migration/upgrade safe. If they don't work for you the go ahead and use the schema extension tool.

    HTH, Barry.

  • 0 over 8 years ago
    Hi, Barry.

    It would be good if we could reference the field from vb.net through the "friendly name", and not as "customerpropertyxx". I think it's more undestandable this: "If $empType$ = blah blah" than "if $customproperty05$ = blah blah".

    Is there a way to do it without extending the schema?


    Thanks a lot!
  • 0 over 8 years ago
    Hi,

    Unfortunately not .. the column names are fixed so if you want use names you recognise then it will have to be schema extensions.

    Regards, B.