Skip to main content

Standardize the Platform, Not the Solution -- Assimilation is Futile

Many organizations are plagued by incompatible software solutions that proliferate in multiple departments.  These solutions are expensive to support because they may require different skills from developers and system administrators. The quality of data also suffers because records are updated in one department and not another. The result is a search for a single system that will rule them all.

If this sounds familiar, it is because the desire for a monolithic and comprehensive software solution is timeless and universal.    The problem is that this quest is futile, and has been shown repeatedly to fail by large and small organizations.

Politics is usually the reason that a universal solution fails, not technology.   Individual departments know their data much better than anyone else, and are justifiably reluctant to give up control.

Change is also the archenemy of the monolithic solution.  It takes time to document and implement requirements, and these business needs are subject to change.  A fast cycle for implementing changes is a valuable asset for any organization.

Does the quixotic nature of universal solutions mean that no standardization can succeed?  No, it turns out that some standards can help you save time in procurement, development, testing and training.  The most important standard is to set a technology platform to encourage compatible solutions for your departments.

The best items to standardize are:
  1. The database. The database is the heart of most solutions. Supporting multiple databases will drive up software and integration costs.  
  2. Workflow engine. If an enterprise can standardize on workflows across departments, many headaches are eliminated.
  3. Services layer for user interfaces. Multiple interfaces are required, especially for mobile apps, so a standardized approach will save time. The Model View Controller (MVC) architecture decouples the user interface from the data and business rules for better performance and flexibility.
This standardized approach will require less expensive integration efforts, allowing more resources to be spent on customizing the workflows and user experience for your unique business needs.

Popular posts from this blog

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …