TABLE OF CONTENTS

• Shared Items Between Projects
• Best Practice Guidelines
  • Example Scenario
• Further Support

When planning a multi-project implementation in ManagementStudio, review the following guidelines to ensure you understand which features and data types support sharing between projects.

Shared Assets 

The table below outlines which Asset types can be shared across projects and provides relevant notes.

Best Practice Guidelines

• Custom Fields: Fields such as CustomFlagX, CustomPropertyX, and CustomListX are shared across all projects for shared asset types. Care should be taken when making these visible in shared projects as the Display Name of each fields can differ between projects, but the value will always be the same. It's generally better to use Project Properties.
• Project Fields: Fields such as ProjectFlagX, ProjectPropertyX, and ProjectListX are unique to each projects for shared asset types. This means that Project Fields for all assets (e.g. ProjectProperty1) can be repurposed across all the projects.
• Drop-down Lists: Drop-down values configured in the Details tab are not carried over into child projects and must be re-created where needed. 
• Asset Sharing Recommendations:
  • Avoid sharing primary, target assets (e.g., applications to be retested or remediated in the new project). Instead, export these items from the original project and import them into the new project. This approach allows you to redefine custom fields as appropriate for the new context.
  • Share secondary or supporting assets (e.g., User Migrations, Devices) from previous projects to maintain consistency and reduce duplication.
  • If needed, add connectors within the new project to establish relationships between assets (e.g., linking users, applications, and devices).

Example Scenario

• A Windows 10 project exists in ManagementStudio.
• A new Windows 11 project is starting.
• Applications require retesting for Windows 11 compatibility.

Recommendations:

• The application strategy depends on whether the Application Custom Fields can be moved into Project Fields or not:
  • Yes: Move the Application Custom Fields into Project Fields within the Windows 10 project. Then share the applications from Windows 10 to Windows 11. The Project Fields can be repurposed in the Windows 11 project.
  • No: If the Application Custom Fields need to remain in place for the Windows 10 project, then the applications from the Windows 10 project should be exported and imported into the Windows 11 project as independent, non‑shared assets.
• Share User Migrations and Devices between the projects if needed.
• Add connectors in the new project to create user-to-app-to-device links as necessary.

Further Support

For additional assistance, visit the ManagementStudio Service Desk to search the knowledge base or create a support ticket.