web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Error '... is not supported when used as part of a data package (bacpac).' when exporting bacpac from SQL Database

(0) ShareShare
ReportReport
Posted on by 370

I'm now in the middle of upgrating data from AX2012 R2 (with SQL Server 2012) to Dynamics 365.

Everything went well during preparation of database "bacpac" file, which will be made in AX2012 and transfer into Dynamics 365 (Tier2 with SQL Azure)

Reference;

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/upgrade-data-sandbox

However, when I run the export command from command prompt, many errors occured as below and the bacpac was not created.

Error SQL71564: The element Full-text Index on [dbo].[VENDTABLE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Full-text Index on [dbo].[ECORESCATEGORYTRANSLATION] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Full-text Index on [dbo].[CATEXTERNALCATALOG] is not supported when used as part of a data package (bacpac).
Error SQL71564: Element Table: [dbo].[BUDGETMODEL] has an unsupported property IsChangeTrackingOn set and is not supported when used as part of a data
 package.....

In this forum, I saw many post regarding import error of bacpac file, but not for exporting.

Have anyone faced and handle the related issue before?

Any reference or comment would be appreciated.

Best regards,
Mai
 

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Hassan_rulz Profile Picture
    3,801 on at

    It seems like issue with the table indexing.. have you tried disabling the index?

  • Verified answer
    Community Member Profile Picture
    on at

    Hi Mai.S,

    As this link shows:https://docs.microsoft.com/en-us/sql/relational-databases/system-functions/full-text-search-and-semantic-search-functions-transact-sql?view=sql-server-2017

    _5563B783_8.PNG

    Full-text search can be used in the sql-server but not in the azure database.So you should disable the index.

    Besides according to the link:https://docs.microsoft.com/en-gb/azure/sql-database/sql-database-transact-sql-information

    ,there is many other T-SQL features and statements you should eliminate when you do the database migration.

    Best Regards

    Tom Cai

  • Mai.S Profile Picture
    370 on at

    Hi Hassan and Tom,

    Thank you both for your suggestions.

    As Full-text search is no longer available in Azure SQL database,

    I had to delete all Full-text Index in SQL Server 2012 database to create bacpac file. (disabling was not enough)

    Thank you for your support.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans