![]() ![]() To avoid the undesirable behavior just described, do not use the Switch Branch feature when making changes to business objects that change the underlying database schema, and make all changes in a separate workspace and a separate branch. Sample data rows that you added previously. (business object field) that you added in Step 1. If you switch back to Branch A, VB Studio again adds the column.VB Studio deletes theīusiness object field (and the sample data rows) that you added in Branch A, so thatĭatabase schema matches the business object in Branch B. You switch to another branch (Branch B) where the instance of the business objectĭoes not have the new field that you added in Branch A.VB Studio adds a column to the database schema and the sample ![]() You add a new business object field and some data rows to a business object in aīranch (Branch A).Rows in one branch, and then switch to another branch, the sample data rows are lost. If, for example, you add a business object field and sample data When you switch aīranch, VB Studio changes the database table to match the business object on the branch VB Studio maintains one database schema per workspace. Studio, we recommend, as a best practice, that you perform these tasks in one workspaceĪnd one branch. When creating business objects, business object fields, or adding sample data in VB The apps in your visual application and other clients access the business objects via their REST endpoints. Business objects are stored in a database. Like a database table, a business object provides the structure for data. A business object is a resource, such as an invoice or purchase order, similar to a database table it has fields that hold the data for your application. ![]()
0 Comments
Leave a Reply. |