ビジネス バリュー
Customers that use custom schema names in the same database to partition their database for dev, test, and prod can now use environment variables to save time when deploying their application from dev to test and to prod. Rather than manually dropping and re-adding data sources between dev, test, and prod, authors can use environment variables to speed up the transfer between these environments.
機能の詳細
Many customers use schemas for DEV, TEST, and PROD to manage Application Lifecycle Management (ALM). To access a table, you must specify the schema explicitly, as the default "DBO" schema cannot be assumed. This requires a four-part reference: server, database, schema, and table.
For example:
<myserver>/<mydatabase>/<DEV>/<mytable>
versus
<myserver>/<mydatabase>/<PROD>/<mytable>
Current SQL environment variables only support server and database, assuming separate databases for DEV and PROD, making four-part references impossible. This feature allows specifying the schema as an environment variable. Power Apps binds to specific table names, which must remain consistent across environments, though schemas may vary. This feature enables customers using schemas for DEV, TEST, and PROD to utilize SQL environment variables in their applications.
有効対象:
Users, automatically
この機能はユーザーに対するユーザー エクスペリエンスの変更を含み、自動で有効化されます
