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

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.

Parents
  • 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!
Reply
  • 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!
Children
No Data