How to Apply Hotfix and Create Deployable Package in D365
Deploy SSRS Reports Manually - Dynamics 365 for Finance & Operations On Premises Installation
In an D365FO On Premise Installation you can raise an issue where the SSRS Reports are not deployed.
From my understanding it should be a Bug that will be fixed soon.
However, you can deploy them manually following the below steps:
- Go to the SSRS nodes.
- Access to the C:\ProgramData\SF\Rep_xx\Fabric\work\Applications\ReportingService_Appxx\ReportingBootstrapperPkg.Code.x.x.x.xxxxxxxxxxx\Scripts folder
- Open PowerShell in Admin Mode. So Click on the File menù\Open Windows PowerShell\Open Windows PowerShell as Administrator
- .\DeployAllReportsToSSRS -PackageInstallLocation \\AOS1SERVERNAME\c$\ProgramData\SF\AOS_xx\Fabric\work\Applications\AXSFType_Appxxx\AXSF.Code.x.x.x.xxxxxxxxxxx.zip.0\Packages -ReportServerIp XX.XX.XX.XX
Data-Driven Decision Making: How To Take Advantage For Business Success
10 new features coming in 2018 for Dynamics 365 for Finance and Operations
December Release – Dynamics AX2012 R3 update
The Dec release for Dynamics AX 2012 R3 version is now available in LCS on the updates tile inside your R3 project. This update represents a typical collection of smaller functional improvements and technical fixes. Bugs were fixed in all areas with enhancements found in Warehouse & Transportation, Master planning, Service Management, Project Accounting, Inventory, Retail, DIXF, APAC & Europe localizations. Please see the full list of hotfixes below to search for your specific issue newly included in this release. This release is a cumulative package including all other fixes released in the prior CU13 update. This release is intended to give visibility into fixes recently shipped for R3, including some features and design changes that are newly released in this month.
Here are a few details related to this release:
- Primary Build: 6.3.6000.3475
- Number of Application hotfixes: 84
- Number of Binary hotfixes: 12
Details of the install process can be found here: https://technet.microsoft.com/en-us/library/hh538446.aspx#PackageR3
What is included in this month’s release?
Design Change Requests, Feature Requests & RegFs
KB Details | Description of issue or change request | Description of enhancement |
KB_4051245 | Excel format and electronic XML format of transport tax declaration are changed for 2016 reporting
| The changes in the hotfix enable the changes for the excel format and electronic XML format of the transport tax declaration for 2016 reporting in Microsoft Dynamics AX 2012 R3. |
KB_4041655 | CH - Swiss direct debit ISO20022 (only CH-DD, no CH-TA=LSV+/BDD) - AX 6.3 | Implemented new Payment Format for Swiss direct debit and reports based on SEPA DD reports.
|
KB_4056454 | Dropping the indexes that are created outside of AOT. | The changes in the hotfix allow you to add the "dropindexcreatedoutsideofaot" registry to determine whether to drop the indexes created outside of AOT.
|
KB_4056915 | Performance Issue:- When item bar codes are quickly scanned into Modern POS (MPOS), it cannot handle this quickly enough, which starts to concatenate the barcode strings, and you have to slow down or restart the transaction completely. | The changes in the hotfix update the keyboard listener to be smarted when detecting scans and how scans are processed. It also considers more delimiters that designate the end of a scan. |
KB_4052311 | This regulatory feature addresses the changes in SPED Contributions payout to attend the practical guide 1.25. | The changes in the hotfix enable the update for Brazilian SPED Contributions in Practical guide 1.25. |
KB_4056851 | As per the current design when user enters transaction amount greater than authorized amount system doesn’t validate this and allows user to create the line. | To fix the issue, system will validate the transaction amount. If budget controller is on, travel requisition amount is mapped to expense line and amount is greater than budget amount then system will not allow |
KB_4056794 | There is an error message of an incorrect entered tender declaration amount and recount issues. The shift cannot be closed due to the wrong tender declaration amount. | The changes in the hotfix resolve the reported issues as POS will provide more information in the error message. MPOS will ask you to confirm saving the wrong value or not, When the number of recounts reach the maximum recount limit, disallow saving the declared amounts |
KB_4057006 | When an item is counted in a warehouse, another counting journal cannot be created in a different warehouse for the same item. You cannot create a new counting journal due to the following error message: "Item XXX is locked for updates in warehouse A because it is being counted." | The changes in the hotfix allow the same item to exist in multiple counting journals for parallel import. When the policy on the counting journal name of "counting status registration policy" is set to enabled, the original behavior is kept. When it is set to disabled, the new behavior takes place. |
KB_4053536 | Assume that you try to do month end reconciliation from the Accrued purchases report to the general ledger module. There are differences for any catch weight (CW) item that has a different quantity than the default between what is posted in the purchase receipt journal and the amount that shows on the Accrued purchases report. | The changes in the hotfix makes sure the Accrued purchases report is correct when the quantity receipt differs for the CW items. |
KB_4052761 | Starting from December 2017 Russian indirect taxes declaration must be created in the new format. | The solution is to make changes in the existing format, so it would satisfy new requirements. |
KB_4056546 | When you do management sales picking work, it is missing the related work inventory transactions. | The changes in the hotfix make sure that the sales picking work has the related work inventory transactions as expected. |
Fixes Released
KB Number | Complete Feature Path | Title |
KB_4057287 | \AX Retail | "Drawer URL" in Japanese translation is wrong |
KB_4056904 | \AX Retail | Brazil/BRA: "Identify customer for sales" error when executing the payment for products with price over 10,000.00 |
KB_4056384 | \AX Retail\Solution\Customers and loyalty\Customers and Groups | New customers created by POS don't copy the "Mandatory credit limit" property from the default customer |
KB_4056052 | \AX Retail\Solution\Financials\Statement Calculation | "You must select a" error when trying to calculate retail statements |
KB_4057807 | \AX Retail\Solution\Order management\Back Office (Cross-Channel) Fulfilment of Retail Store Customer Order | SO status remains open for non-stocked items after posting packing slip |
KB_4056004 | \AX Retail\Solution\Order management\Taxes | Error required to be raised when tax calculation fails on POS |
KB_4057289 | \AX Retail\Solution\Store operations and POS\Sales, Returns and Other Transactions | Cannot return a customer order after installing hotfix KB4052118 |
KB_4057286 | \AX Retail\Solution\Store operations and POS\Sales, Returns and Other Transactions | Refund shipping charges functionality doesn't work for return orders in POS |
KB_4057288 | \AX Retail\Solution\Store operations and POS\Sales, Returns and Other Transactions | Operator name doesn't get printed for the "Customer account payments" receipt type on POS receipt transactions |
KB_4056836 | \AXL\APAC localizations\Japan | Japan/JPN: Getting stuck in a loop when calculating payment date with payment terms of cutoff date |
KB_4056084 | \AXL\Europe Localizations | Italy/ITA: Italian sales tax payment report shows a wrong invoice number in case of Split payment |
KB_4054747 | \AXL\Europe Localizations | United Kingdom/GBR: The Control list report is missing information if you are restricted to payment company only |
KB_4057613 | \AXL\Europe Localizations\Eastern Europe\Poland | Poland/POL: Polish SAF reports are extremely slow |
KB_4056551 | \AXL\Europe Localizations\Europe Common\Intrastat | Netherlands/NLD: Intrastat transactions shows the country code value with three digits but not two digits |
KB_4041867 | \AXL\Europe Localizations\Italy | Italy/ITA: Depreciation run date editable in vendor orders isn't transferred on the value model |
KB_4042264 | \AXL\Europe Localizations\Italy | Italy/ITA: The new up and down buttons in the Setup form don't work as expected in Microsoft Dynamics AX 2012 R2 Italian Periodic VAT payment communication |
KB_4057323 | \AXL\Europe Localizations\Russian Federation\AP AR | Russia/RUS: Advance adjustment posting error for two product types |
KB_4055464 | \AXL\Europe Localizations\Russian Federation\Sales tax | Russia/RUS: "Voucher XXX, date YYY" error when posting a payment journal and closing the sales book |
KB_4058015 | \AXL\Europe Localizations\Russian Federation\SCM | Russia/RUS: "Quantity XXX cannot be" error when trying to do shipment cancellation |
KB_4056845 | \AXL\LATAM Localizations\Brazil | "Exception has been thrown" error when trying to approve NF-e |
KB_4057623 | \AXL\LATAM Localizations\Brazil | Brazil/BRA: "Exempt base amount" field is wrong when executing the adjustment for the ICMS tax |
KB_4056088 | \AXL\LATAM Localizations\Brazil | Brazil/BRA: Missing fiscal document code (NCM) from item when Product type = 10 and file is rejected by government |
KB_4056089 | \AXL\LATAM Localizations\Brazil | Brazil/BRA: Missing cancel accounting date for a canceled TO invoice in SPED Fiscal file |
KB_4056837 | \AXL\LATAM Localizations\Mexico | Mexico/MEX: "The value of field" error when using CFDI Complement of payment version 1.0 |
KB_4056534 | \AXL\LATAM Localizations\Mexico | Mexico/MEX: CFDI reference form in Sales order doesn't refresh data |
KB_4056903 | \Client | GDPR - Updated privacy notice for AX2012 R3 |
KB_4055044 | \Developer and Partner Tools\DIXF | Error when publishing an entity to an entity store |
KB_4057660 | \Developer and Partner Tools\DIXF | DIXF employee entity doesn't populate the retail job staff data |
KB_4057505 | \Developer and Partner Tools\DIXF | Mult task doesn't work in entity store |
KB_4056862 | \Developer and Partner Tools\DIXF | "Cannot create a record" error when importing the data from Product entity |
KB_4057308 | \GFM | "The value X in" error when entering multiple lines in an invoice journal |
KB_4057025 | \GFM\Accounts Payable | Implement 1099-OID form changes for 2017 for AX2012 R3 |
KB_4044003 | \GFM\Accounts Payable\Invoice Journals | Calculated sales tax amount is doubled in invoice journal inquiry when posting an invoice |
KB_4057313 | \GFM\Accounts Payable\Invoicing | Cannot view a packing slip journal after canceling a delivery slip journal |
KB_4056267 | \GFM\Accounts Payable\Invoicing | Three-way matching policy violation message while posting partial invoice |
KB_4055441 | \GFM\Accounts Receivable\Customer | United States/USA: Customer aging snapshot takes up too much resource |
KB_4042056 | \GFM\Accounts Receivable\Sales Order Invoicing | AIF outbound port value mapping for units fails |
KB_4056077 | \GFM\Accounts Receivable\Sales Order Invoicing | Open customer invoice print management issue |
KB_4053691 | \GFM\Accounts Receivable\Sales Order Invoicing | Intercompany PO invoicing never finishes when GL allocation and charge activated |
KB_4054950 | \GFM\Budget\Budget Control | Cannot associate the BRE in a subsequent budget control maintenance utility |
KB_4046849 | \GFM\Budget\Budget Control | Carry-forward amounts appear when the carry forward option not included is selected |
KB_4056914 | \GFM\Cash Management | Selecting bridged transactions with a different offset account than the fixed offset account doesn't throw an error |
KB_4056162 | \GFM\Cash Management\Currency Revaluation | Accounts receivable simulation is extremely slow |
KB_4055421 | \GFM\Cash Management\Customer\Payments and Settlement | Incorrect exchange rate loss for a customer invoice with Discount + Payment Schedule with several installments |
KB_4056824 | \GFM\Cash Management\Vendor\Payments and Settlement | Payment journal posting is slow due to delete on spectrans |
KB_4056927 | \GFM\Expense Management | United Kingdom/GBR: Mileage doesn't calculate correctly when adding 2 lines in the different fiscal year within the same natural year |
KB_3195987 | \GFM\Fixed Assets | Reclassification with main value model and derived value model doesn't use the right acquisition account from posting profile |
KB_4052223 | \GFM\Fixed Assets | Depreciation isn't calculated properly |
KB_4056925 | \GFM\General Ledger | "The transactions on voucher" error when posting a journal after modifying a customer account |
KB_4057018 | \GFM\General Ledger\Reports | Large amounts of rounding variance is shown under totals on ledger trans open report |
KB_4057303 | \Human Resources\Payroll | 2012 R3 Payroll Tax update 2018-R1 for the United States |
KB_4056299 | \Human Resources\Payroll | United States/USA: Distribute earnings form doesn't show premium earnings |
KB_4057428 | \Public Sector\AP | Purchase order year-end process fails for multiple line project PO's that are tied to a project budget allocation |
KB_4057722 | \SCM\Inventory Costing\Cost Module | No financial dimension on price variance |
KB_4056406 | \SCM\Inventory\Consumer Goods Distribution\Batch Management | "No line(s) selected or" error when resetting the batch disposition code in the On-hand inventory area pages |
KB_4056289 | \SCM\Inventory\Consumer Goods Distribution\Batch Management | "Same batch reservation conflict" reserves incorrect quantities after a quantity changes on a sales order |
KB_4055461 | \SCM\Inventory\Inventory Management\Shelf Life Management | Shelf advice date, Best before date and Expiration date are set to strange values when the manufacturing date is cleared on a batch |
KB_4056404 | \SCM\Planning\Intercompany Planning | Intercompany demand is ignored if MRP runs with non sys-admin role |
KB_4057156 | \SCM\Planning\Master Planning | "Cannot delete a record" error when executing MRP |
KB_4055760 | \SCM\Planning\Master Planning | MRP performance potential optimization during scheduling |
KB_4056400 | \SCM\Planning\Master Planning | Error when executing the Create journal lines for proposed minimum inventory levels in batch model |
KB_4055200 | \SCM\Planning\Master Planning | Finite capacity causes Scheduling Slowdown during MRP in Batch with multiple Threads |
KB_4043458 | \SCM\Planning\Planned Orders | Financial dimensions incorrectly copied when adding an item to PO created from planned order |
KB_4036655 | \SCM\Procurement\Purchase Orders | The system doesn’t display Discount percent and Discount options in the Overwrite prices and discount form when Purchase order lines are copied from purchase order type “Journal” by using "Copy from all" option with no unit price on the first line |
KB_4057164 | \SCM\Production and Shop Floor\MES | "There is a chronology" error when trying to calculate time in shop floor control |
KB_4057603 | \SCM\Production and Shop Floor\Production Journals | Accept error checkbox is marked after posting a report as finished journal |
KB_4057297 | \SCM\Sales | "You must select a" error when reversing a write-off from the Deduction workbench |
KB_4055371 | \SCM\Sales\Rebates | Cannot delete payment journal if deduction line is deleted from it |
KB_4055205 | \SCM\Sales\Sales Orders | Incorrect subtotal amount in sales orders with total discount and zero sales tax |
KB_4057148 | \SCM\Sales\Sales Orders | RMA Find sales order doesn't use method of payment from original SO |
KB_4055781 | \SCM\Service Management | Service orders don't populate to the service objects on manually created lines |
KB_4046691 | \SCM\Sourcing\Request for Quotes | Wrong RFQ when sending and publishing to vendor portal after applying hotfix KB3859374 |
KB_4055611 | \SCM\Sourcing\Vendor Agreements | Issue when multiple purchase agreements are effective during the same period |
KB_4056300 | \SCM\Warehouse and Transportation\Warehouse Management\Load Management | "Unblock work" functionality causes work with dependent replenishment work to become unblocked |
KB_4056833 | \SCM\Warehouse and Transportation\Warehouse Management\Work and Worker Management | WHS is missing location in second work |
KB_4057189 | \SCM\Warehouse and Transportation\Warehouse Management\Work and Worker Management | Date entry on Vendor batch page in WMDP doesn't keep date format specified |
KB_4051645 | \SCM\Warehouse and Transportation\Warehouse Management\Work and Worker Management | Wrong put location when using location directive with query based on batch disposition code |
KB_4056315 | \SI\Project Accounting | "XXX cannot be reserved" error when changing the warehouse on a PO |
KB_4055591 | \SI\Project Accounting\Commited Costs | Committed field on Project contracts displays value after canceling workflow on Timesheet |
KB_4055590 | \SI\Project Accounting\Project Control | Wrong project posting type when generated from expense report |
KB_4056317 | \SI\Project Management\Projects | Borrowing project with pending intercompany hours at various stage can be deleted |
KB_4056319 | \SI\Project Management\SCM Integration | Project ID is missing for production and purchase order when generated through master scheduling for a project sales order |
KB_4057249 | \Workflow | Workflow delegation doesn't validate users entered manually |
Five reasons why every organization should conduct regular cybersecurity self-assessments
Remove prefixes form table fields created from EDTs using D365FO Ninja DevTools
Collection letters in Dynamics 365 for Finance & Operations
Exception Handling in Dynamics 365 Operations and Finance
Exception Handling
Partition in Dynamics 365 Operations and Finance
To create a new partition, you can put the partition form name at the end of the AX client URL.
https://usnconeboxax1aos.cloud.onebox.dynamics.com/?f=partitionadministration
Microsoft DLP Dynamics 365 course catalogue – January update
Custom fields: handle with care!
The Microsoft team did release platform update 13 for Microsoft Dynamics 365 for Finance and Operations, Enterprise edition. One of the new features is Custom fields. This feature lets a power user or system administrator configure new fields on existing tables without using the development environment and deploy it on the other environments. It is a neat feature which can be of interest, but you also have to be aware of all pitfalls and downsides. In this post, I will tell you more about the custom fields.
What are the custom fields?
When you are in the need for some additional details on a customer, vendor or worker, usually you would ask a developer for creating fields in the tables and add them on the form using extensions. Then a deployable package is used to move the changes to your production environment. With the new feature in platform update 13, you can now configure the fields. The reason for adding this feature by Microsoft is to provide an easy and cost-effective solution to add simple details to existing tables and use them within Dynamics 365 for Finance and Operations. Using the configuration option, you could save on development, testing and code life cycle.
The process is very easy. Of course, not all users can do it themselves. You have to be a system administrator or have the role Runtime customization power user assigned. It is described on the next documentation page: Custom fields
The next screenshots show some of the steps to create a new field on the customer table which represents a legacy/old customer number. As mentioned in the documentation, start with personalizing the form:
There are options to define your custom field:
Once completed and reloaded the form, you can maintain the new field:
Difference with the development approach
When configuring fields, you cannot control things like indexes and coding to validate or automate entry. These options are available when a developer will create a field in the meta data. When a field is created in the meta data and deployed on all environments, it would also be possible to include this field in new or customized reports. So, it is not possible to configure a field and have the field visible in the development environment for reporting. It is possible to add a configured field to data entities on runtime.
Within an implementation, you have to careful consider if you want to configure a field or needs to have more control options and let a developer create an extension. Fields in the application metadata are more sustainable. In advance, you should know the purpose of this field.
Some important limitations of configured custom fields are:
- Not able to add business logic as it requires coding. (Side note: my company has a Data Validation Framework add-on available which also handles the custom fields)
- Not able to add indexes on runtime. Searching on the field in larger tables can cause slowness.
- Not able to add the field on existing reports.
- Showing the field on forms is done with personalization. Users should add the new field themselves or an administrator can copy a template to all or selected users.
- You cannot control the size of the field. E.g. text fields created with 100 characters will be displayed in a smaller single line field. It is not possible to enlarge the field or make it a multi line.
Expose custom fields on data entities
It is possible to include the new configured fields on existing entities using the Custom fields maintenance form. When enabled, you can use the field in the Data Management features and Open in Excel. Using data management, you could use reporting tools like Power BI to expose your custom field.
Under the hood
When you do configure a custom field, Dynamics 365 will create runtime table extensions and also a physical field on the table in the database.
There are some limitations defined by Microsoft. These constraints were added to prevent issues like performance degradation. The next rules are valid for tables (taken from the documentation):
- The table must be tagged as one of these groups: Group, WorksheetHeader, Main, Miscellaneous, Parameter, Reference, TransactionHeader
- The table cannot not extend another table.
- The table cannot be marked as a system table.
- The table cannot be a temporary table.
When creating a picklist field, a list with possible values are maintained in a table which will be used as lookup when entering the data.
I have tested the custom fields on a table of our own add-on which was also working correctly. Technically, Microsoft did a very good job here.
Also, there is a maximum on the number of fields to be added on a single table using the configurable custom fields option. The maximum number is 20. When creating fields, be careful with lengthy text fields. Too many longer text fields will cause growth of the record size which could lead to performance penalties. Though, it is a bit strange that 20 fields are allowed, where the best practice check in Visual Studio will give a warning if you create more than 10 in one extension.
Handle with care
As stated, there are limitations and you should not provide access to every user to be able to create their own fields. I do think configuring the custom fields should be considered very carefully. Showing the custom fields are presented to the user as form personalization. If a system administrator will push a new “form layout” to all users, earlier created personalizations will be overwritten. Also, a user could easily remove the field himself or reset the personalization without knowing he is losing the new field. So possibly development would be more expensive, but there is a better governance that it will not have negative side effects. If you run into problems, troubleshooting is also costing money…
As mentioned above, searching on non indexed fields and too many large text fields can cause performance issues.
A fellow MVP, Ievgen Miroshnikov, found another danger. A developer could add a table extension ending with _SysCustomFields and add the field with exact the same name (in my example OldNumber_Custom). Then deploy it to an environment where the custom field was created. Assuming the custom field record is not required anymore, delete the field from the configuration. It will then forget that it was included in a deployable package and the field will be physically removed from the database. So, never, ever use fields as developer end with ‘_custom’ and don’t user table extension names ending with ‘_SysCustomFields’. Usually we would not use these keywords, but thinking to “move” the configuration to development based extensions could lead to assumptions and one attempt. So, you are alerted now! Read below for a work around…
Move custom field to development environment
Like stated above, it is not possible to move the custom field one-on-one to Visual Studio. The best would be developing a complete new field as extension (different naming convention). Also extend standard data entity with the new field. Once these changes are deployed , you have an environment with two fields for the same. Export the data using data management. Then you can import it into the new field. Once you have checked this was successfully completed, you can delete the custom field.
There is more…
It is not documented by Microsoft, but you can enable database logging on the custom fields. Just like any ordinary field, you can select the custom field in the list for updates logging.
If you want to learn more about this feature, I will host a MVP session for the AXUG on this topic on Monday, February 12 at 9 AM EST (3PM CET).
That’s all for now. Till next time!
Microsoft Dynamics CommunitySubscribe to this blogger RSS FeedMy book on Merging global address book records in AX 2012
The post Custom fields: handle with care! appeared first on Kaya Consulting.
Microsoft Dynamics Partner Roundup: NAV manufacturing partnership; Supply chain for NAV 2018; ERP Connectors; Partner name change
Restricted Admin Access on development VMs with Platform update 12: What you need to know
D365 platform update 12 (7.3): Admin access changes
![]() |
Prior to PU12 7.3 |
![]() |
With PU12 7.3 |
X++ code to display Scope Type Label from NumberSequences.
Digital transformation brings modern, next generation, enterprise-ready intelligence
[D365/AX7] How to: Create number sequence
Number sequences are used to generate readable, unique identifiers for master data records and transaction records that require identifiers. A master data record or transaction record that requires an identifier is referred to as a reference.
On this example, we are going to create a new number sequence for customer group.
Create a new class that extends the NumberSeqModuleCustomer class and then create the method loadModule_Extension and add the following code:
class NumberSeqModuleCustomer_CFS extends NumberSeqModuleCustomer { public void loadModule_Extension() { NumberSeqDatatype datatype = NumberSeqDatatype::construct(); datatype.parmDatatypeId(extendedTypeNum(CustGroupId)); datatype.parmReferenceHelp("Customer group ID"); datatype.parmWizardIsContinuous(false); datatype.parmWizardIsManual(NoYes::No); datatype.parmWizardIsChangeDownAllowed(NoYes::Yes); datatype.parmWizardIsChangeUpAllowed(NoYes::Yes); datatype.parmWizardHighest(999); datatype.parmSortField(20); datatype.addParameterType(NumberSeqParameterType::DataArea, true, false); this.create(datatype); } }
Important: As we can see on Application Explorer, NumberSeqModuleCustomer belongs to Application Suite model, make sure the model which you are using for development extends this model.
Like in Dynamics AX 2012, we still have to initialize the references manually by creating a Job (Runnable class) with the following code:
class loadNumSeq_CFS { public static void main(Args _args) { NumberSeqModuleCustomer_CFS numberSeqMod = new NumberSeqModuleCustomer_CFS(); numberSeqMod.loadModule_Extension(); } }
Before proceeding build the solution and run it.
On Dynamics 365, go to Organization administration/Common/Number sequence:
Click on Generate button:
It will open Number Sequences Wizard, click on Next button:
Note the number sequence codes and click on the Next button:
On the last page, click on the Finish button to complete the setup:
The last thing we should create is a method to consume our newly created Number Sequence, we are going to create a new extension class of CustParameters table and call it CustParameters_Extension.
[ExtensionOf(tableStr(CustParameters))] final class CustParameters_Extension { client server static NumberSequenceReference numRefCustGroupId() { return NumberSeqReference::findReference(extendedTypeNum(CustGroupId)); } }
And that’s all the steps. Soon I will be posting how to use our Number Sequence.
If you have any doubt about D365 extensibility, I recommend to read Tayfun Yaman’s 3 parts post about it.
