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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Can I modify the existing extensions without the source code?

(7) ShareShare
ReportReport
Posted on by 43

Hi All,

I just join a new company which use BC. I checked the Extension Management and there are several extensions built by ex-developers. I downloaded them and unzip them. I can see all the filename have changed (e.g. from API.Page.al to  _API _.Page.al) and only the code (no comment, no formatting) in the files.

The original source code files are not in company anymore because there is no source control.

Is it safe to modify the existing extensions based on the files I downloaded from Extension Management? I am going to rename the filenames (from   _API _.Page.al to API.Page.al)

Thank you.

  • Suggested answer
    Nyakinyua Profile Picture
    139 on at

    Hi,

    Yes, it’s generally safe. Download Source on Extension Management returns the code the installed extension was built from. Only comments, formatting and file names are lost, and renaming the files is harmless because AL doesn’t depend on file names.

    Before changing anything:
    1. Check that it matches production
    2. Keep the identity ie same app ID, publisher and name in the app.json just increase the version
    3. Avoid breaking changes, don't delete fields or tables. Mark them as obsolete instead and add upgrade code where data moves.

    Best,
    Nyakinyua

  • SP2019admin Profile Picture
    43 on at

    Hi @Nyakinyua , thank you for your answer. May I know what do you mean by “Check that it matches production”?

  • Suggested answer
    N1ERP Profile Picture
    8 on at

    Since the original source code isn’t available, working directly with the decompiled .app files can be risky and hard to maintain. A much cleaner approach is to use BC Object Designer (https://n1erp.github.io/bc-object-designer/).

    This tool lets you:

    • Open .app files without unzipping them.
    • Browse objects (tables, pages, reports, etc.) in a structured way.
    • View the AL source in a more readable format.
    • Export the reconstructed objects into files for building a proper AL project.

    It won’t restore developer comments or formatting, but it gives you a safer and more reliable starting point than raw decompiled files. From there, you can rebuild the extension in VS Code, set up app.json, and put everything under source control for future maintenance.

    In short: BC Object Designer helps demystify the extensions and makes it much easier to recover usable source code, so you can move forward with a clean and maintainable project.

  • Nyakinyua Profile Picture
    139 on at

    Hi SP2019admin, I should have been clearer, the source you download comes from whichever environment you downloaded it in. If that’s a sandbox, it may hold a different version than production, for example a newer or older build, or a test version someone published from VS Code.
    To check, Open Extension Management in production and note the extension’s version (and whether it’s installed as a per-tenant extension).
    Compare it with the version in the app.json of the files you downloaded. They should be identical.
    If they differ, download the source again from production.

    I hope I have answered your question.

    Best,
    Nyakinyua
     

  • Suggested answer
    OussamaSabbouh Profile Picture
    20,999 Super User 2026 Season 2 on at

    Hello,

    Yes, assuming your company owns the extension/IP, the source downloaded from Extension Management can be used as a recovery starting point when the extension was published with allowDownloadingSource = true, but I would not modify and deploy it immediately. The downloaded source can lose the original file names, formatting, and comments; those file names are not technically important because AL object identity is based on the object type/ID/name, so renaming *_API_.Page.al back to API.Page.al is fine. First create a proper VS Code project, preserve the existing App ID, publisher/name, object IDs, dependencies and schema, download the correct symbols, and make sure the recovered source compiles unchanged against the current environment before making any modification. Then put that recovered baseline into Git, increase the extension version, make the change, and test the upgrade of the existing app in a sandbox—do not create a new App ID or uninstall/reinstall it, because that changes the extension lifecycle and can jeopardize its existing data. Also check the extension card for Source/Build metadata first, because newer BC versions can contain a link to the original Git repository/build even when nobody internally remembers it.

    Regards,
    Oussama Sabbouh

  • Suggested answer
    Yash_Mistry Profile Picture
    648 Super User 2026 Season 2 on at

    Hello @SP2019admin,

    First of all, do you really need to modify the existing code? I'll check whether suitable events are available where we can implement the required logic without changing the existing code.

    Also, the file name does not affect the current Business Central environment. Just make sure you have downloaded the source code from the Production environment.

    Thanks,
    Yash Mistry

  • Suggested answer
    Grigorios Mavrogeorgis Profile Picture
    3,944 Super User 2026 Season 2 on at

    Hi, yes, in most cases it's safe. Renaming the files is no problem, the compiler doesn't care about file names, only the object IDs and names inside.

    What matters is the app.json. Keep exactly the same app id, name and publisher, and only increase the version. If the id changes, BC sees a new app and you get a mess with the data in the existing tables. Also don't remove or renumber fields or tables, it's a breaking change and schema sync will stop you, or worse you lose data.

    Before you change anything, I'd download symbols from the same environment, compile the code untouched, then publish it to a sandbox as version +1 and check that everything still works. If that's clean, you know the download is complete. Look at the layouts (rdlc/docx/xlsx) and the translation files too, sometimes they're missing from the zip.

    ►  If this solved it, marking it verified helps others too.       

    Regards,
    Grigorios Mavrogeorgis
    Business Central Consultant & AL Developer

    Work: Gmsoft Limited
    Blog:  insidebusinesscentral
    LinkedIn: linkedin.com/in/gregorymavrogeorgis

  • Suggested answer
    YUN ZHU Profile Picture
    104,246 Super User 2026 Season 2 on at

    No problem. You can go ahead, download and extract the package, and then add your customizations.

    However, it is best to resave each file first. Beyond file naming, some files also have code alignment and formatting issues. If they aren't reformatted and saved up front, tracking clean diffs in version control later could become problematic.

     

    Thanks

    ZHU

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 569 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 375 Super User 2026 Season 2

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 228 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans