Archive of posts tagged Dynamics 365

F&O development with multiple version control workspaces

Posted by on

The usual setup (documented by Microsoft) of version control for F&O is using Team Foundation Version Control and configuring the workspace mapping like this: $/MyProject/Trunk/Main/Metadata k:\AosService\PackagesLocalDirectory $/MyProject/Trunk/Main/Projects c:\Users\Admin123456789\Documents\Visual Studio 2019\Projects This means that PackagesLocalDirectory contains both standard packages (such as ApplicationSuite) and custom packages, i.e. your development and ISV solutions you’ve installed. This works fine …

Continue reading ‘F&O development with multiple version control workspaces’ »

Acceptance Test Library

Posted by on

Acceptance Test Library (ATL) in F&O isn’t a new feature, but many people aren’t aware of it, therefore let me try to raise awareness a bit. ATL is used in automated tests written by developers and its purpose is to easily create test data and verify results. Here is an example of such a test: …

Continue reading ‘Acceptance Test Library’ »

Get-D365Module -InDependencyOrder

Posted by on

Despite the fact that I built a Powershell module for maintenance tasks of AX 2009 and AX 2012 environments, I’m not much involved in d365fo.tools module. The credit goes to other people, especially Mötz Jensen. Nevertheless I’ve recently added a small feature to Get-D365Module that you might be interested in. Get-D365Module normally returns modules (packages) …

Continue reading ‘Get-D365Module -InDependencyOrder’ »

HcmWorkerV2

Posted by on

I was asked to investigate why some changes disappeared from Employess form in F&O. If I open Human resources > Workers > Employees and right-click the form, it shows that its name is HcmWorker. That’s expected. But it’s a lie. There is a feature called Streamlined employee entry (HcmWorkerV2Feature class) and if it’s enabled, another form …

Continue reading ‘HcmWorkerV2’ »

Method as a parameter (in D365FO)

Posted by on

We usually have methods where the logic is written in code and it just receives some data in parameters. But sometimes it’s benefitial to allow the caller code to define a piece of logic by itself. For example, I can write code to filter a collection and let consumers decide what condition should be used …

Continue reading ‘Method as a parameter (in D365FO)’ »