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 :
Dynamics 365 Community / Forums / Business Central forum / Dynamics 365 Buisness ...
Business Central forum

Dynamics 365 Buisness Central On Premise issues

(0) ShareShare
ReportReport
Posted on by Denny1986 140

Hi Experts,

Now we ecountering servial problems in Dynamics 365 Buisness Central On Premise version 13.3 environment.

1 In the On Premise system, when we import the license for the first time, the 365BC can be opened succesfully. When the license is updated, after we import the license once again,

the 365BC can't be open anyomore, it show "AN error has occurred".

2 Before we can an extension based on version 14 365BC sandbox environment, the extension can be deployed in version 14 on premise 365BC environment successfully,

but we can't publish it in the extension in version 13 on premise 365BC environment, it show error " your program does not allow you to publish ''XXXXX".

The problem is we import the same license file in version 13 and 14 365BC on premise environment, so we confuse with this problem.

Does anyone has any idea about these two issue?

Regards

Thanks.  

Categories:
Other
  • Hannes Holst Profile Picture
    Hannes Holst 5,767 on at

    Hi,

    You can't use an Extension for BC14 in a BC13 version.

    It's not backward compatible.

  • Denny1986 Profile Picture
    Denny1986 140 on at

    Hi Hannes,

    Thank you for your infomation. 365BC is upgraded to version 14 since this spring, so currently we can only use 365BC 14 version container for dev and testing, and as I know, AL language is not specific some version, how can we know the extension we created is work for which version？And Do you mean the extension we create now can only work for version 14? If we want to create extension for BC13, how can we create the extension?  

    Thanks.

  • Suggested answer
    Stefano Demiliani Profile Picture
    Stefano Demiliani 37,172 Most Valuable Professional on at

    In app.json you have a platform setting: this will control your supported platform (13.0.0.0 or 14.0.0.0). Platform 14 has some differences compared to 13, so your extension could have problem if moved back.

  • Denny1986 Profile Picture
    Denny1986 140 on at

    Hi Stefano,

    in app.json, we config platform as "13.0.0.0", Does it mean our extension can support both BC13 and BC14?

    Thanks.

  • Suggested answer
    Stefano Demiliani Profile Picture
    Stefano Demiliani 37,172 Most Valuable Professional on at

    Platform in app.json is the minimum version of the supported D365BC platform. 

    Maybe can you post your error completely? I’ve not understood if it’s platform or license related.

  • Denny1986 Profile Picture
    Denny1986 140 on at

    Hi Stefano,

    When we publish the extension, it the return error "your program license does not allow you to publish ''XXXXX"."

    Thanks.

  • Suggested answer
    Stefano Demiliani Profile Picture
    Stefano Demiliani 37,172 Most Valuable Professional on at

    This is a license-related problem. What object ranges are you using on this extension? Is your range enabled in your license you’re using?

  • Denny1986 Profile Picture
    Denny1986 140 on at

    Hi Stefano,

    Our id range is from70203500 to 70203824, we can publish with our dev license, but when customer use there live license, they will encounter this error. now the error occour for tabledescription object, we set the permission as R-MDX.

    Thanks.

  • Suggested answer
    Stefano Demiliani Profile Picture
    Stefano Demiliani 37,172 Most Valuable Professional on at

    This is a range for SaaS only and for apps obtained via AppSource. Normally, with this range you can publish on a local sandbox (Docker) with a dev license (partner) but not with a customer license. This is normal.

  • Suggested answer
    Olister Rumao Profile Picture
    Olister Rumao 4,009 on at

    If you still want to try then, use the range from 50100 onwards and add it in Object Range. in App.Json

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

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Business Central

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans