Usually the best way of handling that scenario is to create a view called "tblCustomerMaster" that points to a "base_tblCustomerMaster".
As you add additional columns (or even delete or rename columns), you update [size= 12.16px; line-height: 15.808px]"base_tblCustomerMaster", create a view called [/size][size= 12.16px; line-height: 15.808px]"tblCustomerMasterV2" with the new changes in, and update the original [/size][size= 12.16px; line-height: 15.808px]"tblCustomerMaster" to handle the changes (only needed if you have renamed or deleted columns).[/size]
[size= 12.16px; line-height: 15.808px]I hope that makes sense.[/size]
[size= 12.16px; line-height: 15.808px]Kind regards,[/size]
[size= 12.16px; line-height: 15.808px]Nic.[/size]

Read More...

Hi George,
You need to Add the BoundAttachment first, then you can access it and set the ValueOverride.
It would have worked for your Attributes example if the attribute already had the attachment bound.
Cheers,
Nic.

Read More...