MS Dynamics导航-开发许可基础知识 [英] MS Dynamics NAV - development licensing basics

查看:133
本文介绍了MS Dynamics导航-开发许可基础知识的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我是一名新手自学资产净值.有些查询可能是愚蠢的,希望能听到您的天才专家! 确实与许可框架相混淆.

查询

  1. 我可以识别两种类型的许可证-客户许可证与合作伙伴许可证.客户许可证是ERP产品的许可证,包括系统功能包(启动程序/扩展程序)和用户访问权限(完整/受限用户).合作伙伴许可证是开发合作伙伴所订阅的.这两种类型之间没有关系,对吧?

  2. 是开发合作伙伴,可以对Starter/Extended软件包中预装的任何原始对象(表/代码单元)进行更改.开发合作伙伴是否可以在任何程度上修改/增强系统功能?

  3. 开发合作伙伴向Microsoft注册时,是否获得了将用于创建新对象的一组固定的对象ID?它将为实施NAV的所有客户使用相同的ID集吗?因此,这些ID在全球范围内是唯一的-没有两个开发伙伴拥有相同的ID吗?

  4. 当我使用域帐户连接到RTC时,我在客户许可下充当完全用户(我可以在Departments => administration => General => Users下看到我的用户设置为完全用户).如果我连接到NAV DEV ENVIRONMENT,则可以设计几乎所有表格,但是不能使用任何CODEUNITS.那么,安全性如何在DEV Environment上起作用?

解决方案

根据上下文的许可可以指两种不同的事物:
-应用\开发许可证
-客户端许可证类型

应用程序\开发许可证

Microsoft Dynamics导航的许可模型建立在对数据库中的每个对象(表,表数据,表单,报表,数据端口,XML数据端口,代码单元,MenuSuite,页面,查询)定义读取,插入,修改,删除和执行的基础上,这是对于最终用户,合作伙伴和ISV都是如此.

有不同的众所周知的对象范围,它们具有不同的含义,因此可以根据不同的对象编号来假设不同的参与者都可以访问,这些对象已记录在文档中.

修改Codeunits的能力是Application Builder粒度的一部分,并不是很多客户购买的,这很可能会解释为什么您可以设计某些对象类型,而不能设计其他对象类型.

Microsoft合作伙伴拥有与解决方案开发者许可等效的功能,该许可使他们可以在基本应用程序范围内修改受保护的表(例如,分类帐表).

颗粒

系统中有一些不错的资源,可获取有关您期望在NAV实例中拥有哪些权限的信息.在Microsoft Dynamics IDE中,您可以访问您的许可证文件(或者您可以将其读取为文本文件,只是在底部进入ASCII时忽略即可).

您可以使用数字和名称来查找每个数字用于示例

还有一份您可以执行的报告10313许可权限,将概述范围以及每个许可中您具有的特定权限(RIMDE).

您的Microsoft合作伙伴有权生成许可证报告(详细或摘要),该报告将提供您购买的对象以及分配对象的列表.

在以前的许可程序(如业务就绪许可"(BRL))中,您必须分别定义和购买每个颗粒.

最近,Microsoft已转移到永久许可和订阅许可,该许可提供了您可能会使用的大多数应用程序领域.

对象分配

Design Granules带有对特定对象的访问权限,如果您需要对数据库中的对象的其他访问权限,则必须单独购买它们,然后由Microsoft合作伙伴进行分配.

例如,购买"10个其他表"将授予您10个表的权利,然后需要通过为数据库中的表选择特定的对象ID并添加安全性将这些表分配给您的许可证.

发展

在Dynamics导航实例中进行开发的主要参与者有几种:

Microsoft解决方案合作伙伴

这些往往是针对客户的开发,这是对现有表格和对象,错误修复程序以及其他可能仅适用于特定客户的其他项目的修改.

大多数此类开发是在现有Microsoft Dynamics导航对象范围内完成的,或者如果创建了新对象,则在客户设计区域(50,000-99,999)内完成.

具有内部技能的客户通常也可以在此范围内进行开发,因为权限在客户范围"内.

独立软件供应商(ISV)

这些也是Microsoft合作伙伴,但他们专注于为多个客户开发解决方案,这些解决方案将被安装到一系列数据库中,并在认证合作伙伴设计区域(100,000-999,999,999)中工作,所有客户使用的这些对象都是相同的.

请注意,Microsoft解决方案合作伙伴无法像最终用户一样自动获得修改其所需的所有ISV对象的访问权限,并且在某些情况下,由于某些原因,它们可能无法修改某些对象满足ISV的需求(这种情况很少见).

客户许可类型

完全用户"确定连接到数据库时使用的客户端许可证类型,它本身并不直接提供安全性.受限用户确实对其访问权限有限制.

您的许可证和安全性设置可以共同确定用户可以拥有的最大安全性,因为您可以向未经许可的对象添加用户许可权,但是由于运行时没有许可权,他们仍将获得一个安全错误(即使对于未获得特定ISV解决方案范围许可的SUPER角色和MS合作伙伴也是如此).

I am a newbie self-learning NAV. Some of queries may be foolish ones, hoping to hear from you genius experts! Really confused with licensing framework.

Queries,

  1. I can identify two types of licenses - Customer license vs Partner license. Customer license is the license for ERP product and includes system functionality packages (starter/extended) and user access(full/limited user). Partner license is what a dev partner subscribes to. There is no relation among those two types, right?

  2. Is a development partner able to make changes to any of the primitive objects (tables/codeunits) that come pre-installed with Starter/Extended pack. Is development partner allowed to modify/enhance the system functionality to any extent?

  3. When a development partner registers with Microsoft, is it given a fixed set of object IDs that it will be using to create new objects? Would it be using same set of IDs for all the customers it would be implementing NAV? So, these IDs are globally unique - no two dev partners be having same IDs?

  4. When I connect to RTC using my domain account,, I act as a Full User under Customer License (I can see my user set as full user under Departments=>administration=>General=>Users). If I connect to NAV DEV ENVIRONMENT, I CAN design almost all the tables, but CAN'T any of the CODEUNITS. So, how does security work on DEV Environment???

解决方案

License depending on context can refer to two different things:
- Application\Development License
- Client License Type

Application \ Development License

Microsoft Dynamics NAV's license model is built on defining Read,Insert,Modify,Delete and Execute on each object in the database (Table, TableData, Form, Report, Dataport, XMLDataport, Codeunit, MenuSuite, Page, Query) this is true for both End Users, Partners and ISV's.

There are different well known ranges of objects that have different meaning, so depending on what the object numbers are you can assume different parties will have access, they are documented here

Your ability to modify objects will depend on the Object Design Granules you have purchased from Microsoft via your Microsoft Partner, a list of the ones relevent to design can be found at link

Depending on when you Purchased your Microsoft Dynamics License different ones would have been included in your starter pack, most commonly users have:
- 7110 Report and Dataport Designer
- 7120 Form and Page Designer

These provide you the ability to modify code within Reports and Forms, and themselves include objects for modification within the customer license range.

The ability to modify Codeunits is part of the Application Builder granule which not a lot of customers have purchased, would likely explain why you can design some object types and not others.

Microsoft Partners have what is equivalent to the Solution Developer License which allows them to modify protected tables (Ledger Tables for instance) in the Base Application range.

Granules

There are a couple of good resources within the system to get information about what permissions you can expect to have within your NAV Instance. In the Microsoft Dynamics IDE you can access your license file (or you can read it as a text file just ignore when it gets into ASCII at the bottom).

You can use the number and name to lookup what each one is used for Example

There is also a report 10313 License Permissions that you can execute that will provide an overview of the ranges and what specific permissions (RIMDE) you have within your license to each one.

Your Microsoft Partner has access to generate a License Report (Detailed or Summary) this will provide a list of the objects you have purchased and where they have been assigned.

In previous licensing programs like Business Ready Licensing (BRL) you would have had to define and purchase each granule individually.

More recently Microsoft has moved to perpetual and subscription licensing which provides most of the application areas you are likely to use.

Object Assignment

The Design Granules come with access to specific objects, if you require additional access to objects in the database they must be purchased separately and then assigned by your Microsoft Partner.

For Example Purchasing 10 Additional Tables grants you the right to 10 Tables, that then need to be assigned to your License by selecting the specific object id's for tables in your database and adding the security.

Development

There are a couple of main types of parties that do development within a Dynamics NAV instance:

Microsoft Solution Partners

These tend to do customer specific development, this is modifications to existing forms and objects, bug fixes and other items that are likely to only apply to a specific customer.

Most of this type of development is done within the existing Microsoft Dynamics NAV object ranges, or if new objects are created it is done within the Customer Design Area (50,000 - 99,999).

Customers that have the in-house skills can typically also do development in this range, as the permissions are in the Client Range.

Independent Software Vendors(ISV)

these are also Microsoft Partners but they focus on developing solutions for multiple customers that will be installed into an array of database and work in the Certified Partner Design Area (100,000 - 999,999,999) these objects used will be the same for all customers.

A note is that Microsoft Solution Partners, do not automatically have access to modify all ISV object they need to be provided access to the object ranges the same as an end user would, and in some cases maybe unable to modify some objects due to the desires of the ISV (this is rare).

Client License Type

The Full User determines the client license type that is consumed when you connect to the database, and it self does not directly provide security; the Limited user does have a restriction of what it can access.

Your License and Security set-up work together to identify the maximum security that a user can have, as you can add permissions to a user to an object your not licensed for but as the runtime will not have permission they will still get a security error (this is true even for the SUPER role and MS partners that are not licensed for a specific ISV Solution Range).

这篇关于MS Dynamics导航-开发许可基础知识的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆