Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Migration - BC14 -->...
Small and medium business | Business Central, N...
Answered

Migration - BC14 --> BC Cloud Data in Custom field not updated

(0) ShareShare
ReportReport
Posted on by Isa Tahiri 20

Hello,

I'm a bit lost on one migration. 

My customer has a NAV 2013R2 and wants to migrate to BC Cloud. Until here I did : 

 - NAV2013R to NAV 2018 (C/Side + DATA migrate)

 - NAV 2018 to BC14 (C/Side + DATA migrated)

In the BC 14 the customization is still in C/Side (visible from develop)

If i run the web client in BC14 I see the custom field in standard tables and custom tables and respective data. 

Then i created A VS CODE Project with all extenstions (uses TXT2AL) and deployed the app in BC Cloud. 

I see custom field fields of standard tables and custom tables in BC Cloud.

Then I ran the  cloud migration tool in order to bring data. 

Here is the problem : All standard data were migrated to BC cloud but not my custom data. 

Can someone please advice me on what is going on here ? 

In BC 14 there is no way to import the same extension in the web client as the custom fields and tables already exist. 

Thanks for your help. 

BR

ISA

  • Isa Tahiri Profile Picture
    Isa Tahiri 20 on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    Thank you for this important info.

    It is a pity that docs does not say that clearly. 

    I'll definitely do the intermediate upgrade to 17.2 onprem. 

    Thanks again

    BR

    ISA

  • Suggested answer
    THE Italian Profile Picture
    THE Italian on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    Yes. It is a must.

    FAQ | Microsoft Docs - Business Central | Microsoft Docs

    it does not make any difference if you have just one small table or 1000 tables. 

  • Isa Tahiri Profile Picture
    Isa Tahiri 20 on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    Hi,

    One more question. My customer is in BC14 CU18. According to the compatibility matrix in MS web page, the Cloud data migration should work for standard tables. Are you saying that we still strongly should upgrade BC14 CU 18 to BC 17.2 in order to migrate in BC Cloud ?

    My case is pretty simple, 8 small tables to migrate feel that migration to 17.2 is huge job for not much customizations.

    Thank you for your answer.

    BR

    ISA

  • Isa Tahiri Profile Picture
    Isa Tahiri 20 on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    Thank you very much DUILIO TACCONI  !

    Now it is pretty obvious. In MS the documentation this way is not enough emphasized from my point of view.

    I'm just doing it now and it seems to work.

    BR

    ISA

  • Verified answer
    THE Italian Profile Picture
    THE Italian on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    These will never move into the cloud until they are transformed into AL tables.

    The best advice is always to move to the exact major build and update as the cloud store at the moment (currently 17.2).

    If you need to have this moved in the cloud too, then you must move your C/AL tables into AL tables.

    Below just a raw description how you could do that. I am dividing this in A. CUSTOM TABLE and B. CUSTOM FIELD IN STANDARD TABLE

    A. CUSTOM TABLE

    1. Create a C/AL clone of Custom Table with another number and call it e.g. "TEMP Custom Table"

    2. Move all the data content from Custom Table to "TEMP Custom Table" through C/AL codeunit

    3. Delete Custom Table from Object Designer and synchronize with force (table must be deleted in SQL Server)

    4. Regenerate symbols

    4. Deploy AL table called Custom Table with exactly the same data structure and number (e.g. converted through txt2al.exe)

    5. Move the data from TEMP Custom Table to Custom Table using AL Codeunit

    6. Delete TEMP Custom Table (if you like), synchronize and regenerate symbols

    B.  CUSTOM FIELD IN STANDARD TABLE

    1. Create a C/AL Table that contains the primary key fields of the standard table and the CUSTOM FIELDs

    2. Move all the CUSTOM FIELDs content from STANDARD Table to the new table through C/AL codeunit

    3. Delete standard table CUSTOM FIELDs from Object Designer and synchronize with force (fields must be deleted in SQL Server)

    4. Regenerate symbols

    4. Deploy AL Table Extension with exactly the same field data structure and number

    5. Move the data from Temp table in the Table Extension fields using AL Codeunit

    6. Delete TEMP Table (if you like), synchronize and regenerate symbols

  • Isa Tahiri Profile Picture
    Isa Tahiri 20 on at
    RE: Migration - BC14 --> BC Cloud Data in Custom field not updated

    I guess there is no impact but just want to add that at the moment i did only table extensions. (no page extensions)

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans