Marck Anthony Payanay

When installing a solution as a Template Item via the Power Platform Catalog, the installation can fail because the generated Dataverse schemaname exceeds the current 100-character limit.

This is especially limiting for solutions that include components such as Copilot Studio bots, topics, triggers, cloud flows, and other named solution assets. These components often require meaningful business names so makers, admins, and support teams can clearly understand their purpose.

The issue is that the failing schemaname is system-generated, immutable, and includes values such as the publisher prefix, topic/flow name, component details, action name and GUID. Makers do not have direct control over the final generated value, yet the Catalog installation can fail because of it.

Requested improvement:

Please improve this behavior by implementing the following:

• Increase the current 100-character schemaname limit for Catalog Template Item scenarios.
• Add pre-validation before publishing or installing a Catalog Template Item so makers are warned before installation fails.
• Use a safer schema name generation pattern
• Provide official documentation explaining how schema names are generated for Catalog Template Items and what naming limits makers should follow.
• Confirm whether this limitation applies only to Copilot Studio botcomponent records or to other Dataverse-backed solution components as well.

Business impact:

The current limitation forces makers to shorten component names in ways that reduce clarity and maintainability. This is not ideal for enterprise-ready solutions where naming standards, governance, ALM, supportability, and reusability are important.

A platform-level fix or clear validation guidance would reduce deployment failures, improve Catalog adoption, and make Template Items more reliable for reusable Power Platform solution distribution.