[Bug] MYSQL Datastore not working

[MYMaj]

Describe the bug

When I try to add Mysql DB, i got this error:
No production revisions found for the 'CDPTabular1' interface in the connector's interfaces.

Steps to Reproduce

pac code add-data-source -a "shared_mysql" -c "shared-mysql-xxx...." -d "serwer,dbname" -t "[dbo].[table]"

Expected behavior

Generated service

Actual behavior

Error No production revisions found for the 'CDPTabular1' interface in the connector's interfaces.

Environment information

• VSCode
• Connection to MSSQL works
• From Power automate i can use this connection and read tables

[eschavez]

Thanks for reporting this. The error "No production revisions found for the 'CDPTabular1' interface in the connector's interfaces" means our CLI couldn't find the tabular data interface definition in the MySQL connector's published metadata — which is required for pac code add-data-source to generate the typed service layer.

We're investigating whether this is a MySQL connector manifest gap (i.e., the connector doesn't expose CDPTabular1 in its interface revisions) or a CLI-side resolution issue. A few questions that will help us narrow it down:

1. Which PAC CLI version are you running? (pac --version)
2. Can you share the full connector API ID you're using (the shared_mysql-xxx portion)? Redact any credential parts.
3. What region/environment type is your Power Platform environment (commercial, GCC, etc.)?
4. Does pac connector list show the MySQL connector as available in your environment?

We'll update once we've confirmed the root cause.

[MYMaj]

1. Microsoft PowerPlatform CLI Version: 2.8.1+ga4eb71c (.NET Framework 4.8.9325.0)
2. shared-mysql-c58ec471-09dc-4c30-b913-56a82ae83140
3. Region EU
4. Yes, it does
   shared-mysql-c58ec471-09dc-4c30-b913-56a82ae83140 MYSQL /providers/Microsoft.PowerApps/apis/shared_mysql Connected

I use command like that, pac code add-data-source -a "shared_mysql" -c "shared-mysql-c58ec471-09dc-4c30-b913-56a82ae83140" -d "ip,dboname" -t "[dbo].[tablename]"

[ergonza93]

A fix has been checked in and should be available with the next release