Komentáře •

  • @anada1124
    @anada1124 Před rokem

    Great video, Erik. I am also the one who has been frustrated by the complicated licensing.
    One thing I can share is the co-existence of Essential and Premium. When you choose the action of "Update users from Microsoft 365 " on "Users" page, you get an error message telling you not to use both license types in one environment. You can avoid this by using "Security Group" for each environment (i.e. Essential and Premium). The error had been very frustrating but Microsoft recently improved this and we can now use both license types if we pay more for the additional production environment.

  • @shahidullah07
    @shahidullah07 Před 8 měsíci

    @ERIK, thanks for the licensing video, one request can you please plan another video with Essentials & Premium mix environment in one tenant

  • @iamabdullahzafar
    @iamabdullahzafar Před rokem

    Hi Erik,
    Thanks for the helpful content.
    I have a question regarding the BC Team member license, are there any specific permission set for Team member? For example, If I want to give all the permission that you have mention, read permission to all the table, modify permission for existing data, and workflow approval etc.

  • @arthrvdv
    @arthrvdv Před rokem

    Always struggling with the Use Case of users registering time sheets in a Power App with Dataverse and using the Dataverse connector in BC to bring over the data to BC and use a Job Queue to post the Time Registrations. The BC part is only the for accounting. The process of registration and approval is completely handled in the Power Platform. Is a correct licensing in the Power Platform sufficient or do all the users also need a Business Central license? What do you think?

    • @Hougaard
      @Hougaard Před rokem +1

      If the timesheets are in BC, then they need at least a Team Member license.

  • @thelect
    @thelect Před rokem

    Hi Erik, according to you, which is the best way to reduce the database dimensions and speed up the performance on Navision (or even BC) when you have several years of data? There is any easy way to archive a company at a date and open a new one with only opening data (as a migration from other ERP to NAV/BC)?

    • @Hougaard
      @Hougaard Před rokem

      BC performance is not really impacted by data sizes, what are you experiencing?

    • @thelect
      @thelect Před rokem

      Not really in BC but in Navision 2017. I have very big tables for item ledger entry and others ledger tables that cause low performances. Any suggestions?

    • @PedroFTeixeira
      @PedroFTeixeira Před rokem

      @@thelect Check the standard data compression reports.

    • @thelect
      @thelect Před rokem

      @@PedroFTeixeira hi, thanks for your reply, but there is no more compression report for item ledger entry. Any idea?

  • @NavNab
    @NavNab Před rokem

    Hello Erik,
    Our customer currently holds premium licenses (NAV OnPrem perpetual). However, they do not utilize the manufacturing and services features, which their previous partner failed to inform them about. As we assist them with the upgrade to BC (OnPrem) and explore the Bridge to the Cloud option, we are considering the possibility of "downgrading" their licenses to essential. This consideration is applicable in two scenarios:
    1. If we proceed with upgrading to BC OnPrem and decide to remain on-premises.
    2. If we opt to utilize the Bridge to the Cloud functionality.
    Could you please let me know if it is possible to downgrade the licenses in these situations?

    • @Hougaard
      @Hougaard Před rokem

      Great question, you better check in with Microsoft :)

  • @YahyaAlZahabi
    @YahyaAlZahabi Před rokem

    Hello Eric,
    Thank you for sharing!
    I have two questions please:
    I have two clients, the first one has one user assigned to “Dynamics 365 Business Central Device” (but does not belong to any group like the one mentioned “Dynamics 365 Business Central Device Users” ) and its working fine.
    First question: How is he able to work if he does not belong to the group that Microsoft mentioned ?
    Second Client, has like 40 users that are shop floor users, I am considering buying “Device” license, so I should buy 40 licenses or just one license and add all the 40 members to the group “Dynamics 365 Business Central Device Users”.
    Thank you in advance.
    Have a good day.

    • @Hougaard
      @Hougaard Před rokem +1

      Both case sounds like the wrong way. If you have 5 machines on your shop floor, then you need 5 devices and the 40 users should be assigned to the group.

  • @robhansen8668
    @robhansen8668 Před rokem

    Hey Erik - Nothing drives me nuts like Microsoft's over complex licensing. One correction to your presentation - Team Members can only write to three custom tables, not 15. In Microsoft's brilliance they created Team Member licenses for both BC and F&O that are not consistent. The 15 custom entities applies to F&O, not BC.

    • @Hougaard
      @Hougaard Před rokem

      Are you sure? 3 tables was the old Light User limit... Do you have the actual error message shown when a Team Member tries to write to number 4?

    • @robhansen8668
      @robhansen8668 Před rokem +1

      @@Hougaard Yes...once a team member tries to write to the 4th non-excluded table, they get an error. I believe it's the standard "You do not have permission..." error. I was confused on this one too...the documentation says 15 entities, but after some online forum discussion with Microsoft a while back they confirmed it is 3 for Business Central and 15 for F&O.

    • @shahidullah07
      @shahidullah07 Před 8 měsíci

      For Business Central you can also use 15 custom tables

    • @AyyKappa
      @AyyKappa Před 3 měsíci +1

      it's 3 tables for BC on-prem

    • @robhansen8668
      @robhansen8668 Před 3 měsíci

      @@AyyKappa I sure wish Microsoft would change this just to align with what the licensing guide says. It would open up many more possibilities for low license cost custom apps that don't get deep into the core of BC.