Obsolete implicit and explicit use of 'with'
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||General availability|
|Admins, makers, marketers, or analysts, automatically||Aug 1, 2020||Oct 1, 2020|
The use of
with, which allows you to work with members using just simple names instead of qualifying these fully, introduces possible uniqueness collisions when multiple extensions contribute to the same objects. To avoid this going forward, we are marking the use of
with, be it implicit or explicit (using the with keyword), as warnings. In addition, we are adding quick actions to fix a file, as well as suppress obsolete warnings for now. At some point, we will change this to errors (one year after general availability at the earliest), requiring use to be refactored.
For a detailed walkthrough of this feature, see the following description: With or without – that is not a question