Wednesday, 9 August 2017

Progressus Software Approved for Microsoft AppSource

Progressus Software is the largest app to be published on Microsoft AppSource.

Progressus Software today announced that their Microsoft Dynamics 365 for Finance and Operations, Business Edition Application (App) has been published on Microsoft AppSource. Progressus Software is available on Dynamics 365 for professional services firms in need of a comprehensive, cloud-based professional services automation solution.
Progressus is next-generation Professional Services Automation and ERP software, mobile-enabled and architected for the Microsoft cloud. The solution adds advanced project accounting and project management to the powerful financial management functionality of Microsoft Dynamics 365 to provide the most advanced business management solution for professional services and project-based businesses.
The approval of Progressus Software on Microsoft AppSource is a significant achievement. Progressus Software is the largest app approved for Dynamics 365 Business Edition by Microsoft. Typical solutions include less than 200 code parts compared with over 800 leveraged by Progressus.

Read complete post here.

Wednesday, 26 July 2017

Sorting cannot be done based on following FlowFields, you must set the security filtering mode to ‘Filtered’.

When we went to do a Cash Receipt- went to Apply Entries. And selected to sort by Remaining Amount and got the below error.

Sorting cannot be done based on following FlowFields in the Cust. Ledger Entry table: Remaning Amount. This is because the record’s security filtering mode is set to ‘Validated’ (as specified by the SecurityFiltering property) and there are active security filters in the system. To sort based on the FlowFields, you must set the security filtering mode to ‘Filtered’.

We need to change the properties of the record variable as indicated below

This error will appear only when you are not SUPER user and set a security filter on the one of the permission sets assigned to user.

Monday, 29 May 2017

The Birth of a Dynamics 365 App

This is the first blog in a several part series on the Progressus Software journey to make the jump from great idea to great App in the Microsoft AppSource for Dynamics 365 Financials.  It is a comprehensive and collaborative effort to make it happen, from all aspects of an organization, and we will hear from each in this series of posts.
For the past few quarters, we have been working diligently to get Progressus Software published on Microsoft AppSource.  It has been a complete team effort to make it on AppSource as quickly as possible.  Some have asked, “Why,” when the real question they are asking is “Why is AppSource such a big deal”?   AppSource is key to the success of two products: both Progressus Software AND Dynamics 365 Financials.  Microsoft announced earlier that Dynamics 365 Financials would handle the core financial aspects of a company, and that Microsoft would rely on the marketplace at large to develop and supply the best and most useful “apps” to replicate and extend the specialized functionality that already exists in some of the current Dynamics products.  For Professional Services organizations that rely on the project accounting functionality found in Dynamics SL, Progressus Software is the bridge that will connect them to the power and flexibility of Dynamics 365 Financials.  Dynamics 365 Financials handles the back office, Progressus handles the project accounting functionality.  The picture that comes to mind is one of a coral colony, where an individual piece cannot survive on its own, but as they mature together the branches build on and strengthen each other.  A very similar concept with Microsoft and Dynamics 365 Apps.   Dynamics 365 Financials is the core, with Apps attaching and multiplying the beauty of the whole.  That is why AppSource is such a big deal, and why we have put so much effort into getting it right.

Microsoft recognized the Progressus effort too, and has tapped Progressus Software to help other folks get their “Apps together”.  We shared our experiences and lessons learned along the way with other potential App makers at the International ISV showcase hosted by Microsoft in Lyngby Denmark in March, with the Canadian ISV and Partner teams in May, and we will even host a full session at Directions 2017 on the process and the thought that goes into creating and marketing an App for Dynamics 365.
As I mentioned earlier, we’ll cover some of the building blocks that need to be in place and operational before you can even submit your App for publication, and we’ll hear from our own Progressus team members in each area.  Up next, our own Progressus Development Manager and NAV MVP Mohana Pallapothu will detail the technical side of the App process.
Thanks for following our quest to get Progressus Software into the Microsoft AppSource, and be sure to check out AppSource regularly to see all of the cool and useful applications that can add to your productivity.  Also, be on the lookout for Progressus Software on AppSource very soon!
Learn more about Progressus Software at

Monday, 17 April 2017

Add Application Area property for D365 App

We need to finish below step in the process of developing the app for financials.

In order to successfully complete the end to end usage scenarios, make sure to set the ApplicationArea for your objects to one of the following values. If the applicationarea is not set to one of these values, the object will not be displayed in Dynamics 365 for Financials. Refer to ApplicationArea Property for more information. 
• #Basic  • #Basic, #Suite  • #Suite • #All

If we have few objects, then we can manually set this property but we have around 250 objects where we need to set this object.

I found below tool in github to add this property using dll.

Thank you so much Ingmar Stieger

You can download the code and create dll using visual studio or you can directly download the dll here

ApplicationArea.exe directory\*.txt -set AREA [-minId nnnnnn] [-maxId nnnnnn]

·        Parameter 1 (* directory\*.txt): Specifies a path and file pattern of text files that should be processed
·        Parameter 2 (-set AREA): Sets all empty ApplicationArea properties to AREA
·        Parameter 3 (-minId nnnnnn): Optional. Process only controls starting with (and including) ID nnnnnn
·        Parameter 4 (-maxId nnnnnn): Optional. Process only controls up to (and including) ID nnnnnn
*Note: Text files can contain one or multiple objects. So you can have either one file per object or multiple objects in one text file.

1.      Export a couple of pages from the C/SIDE client to c:\temp\pages.txt
2.     Set the area to Jobs for all controls starting at ID 1000000000 
      ApplicationArea.exe c:\temp\pages.txt -set Jobs -minId 1000000000 –maxId

It will update the file which we have given in above path.
We can import in to database and check all the fields have ApplicationArea property added.
Once again thank you so much Ingmar Stieger
Please pass it to Ingmar Stieger if someone known him.

Monday, 20 March 2017

Page cannot be saves error while closing matrix page.

Problem: Created a matrix page and entered value in one of the cells and clicked Ok
Below error message appeared.

Solution: please make sure that ModifyAllowed property of the subpage is not set to No.