Start here

How to test your event subscriptions

Many developers have started using the events that are raised in Dynamics NAV, and some have even started adding events to their solutions. There is some concern that a subscription will break if the interface of an event is changed. As a developer, you can verify that the subscription is active by running page 9510,…

from Dynamics NAV Team Blog http://bit.ly/2gQ5XMP

Database deadlock detection and monitoring in Dynamics NAV 2017

Sometimes a programming error in C/AL can lead to users experiencing errors due to database deadlocks. A database deadlock can occur when two sessions try to update the same data, and are acquiring database locks in different orders. For example, let’s imagine two code units 10001 and 10002, which both do updates to records in…

from Dynamics NAV Team Blog http://bit.ly/2gpB4A1

Microsoft Dynamics Marketing today and what comes next – How can you continue using your data?

When it comes to transitioning to the next generation of marketing and customer engagement automation tools from Microsoft, there are a few topics of interest:

  • The life cycle of Dynamics Marketing
  • Migration and My Data questions
  • Licensing questions in relation to the next generation of tools

How customer of Microsoft Dynamics Marketing best migrate to the next generation of marketing tools from Microsoft – “Dynamics 365 for Marketing, Business edition”

As an existing customer of Dynamic Marketing feel free to continue using the product throughout the ongoing subscription period. You may extend your subscription once from now to October 2017. For Direct purchase customer, the subscription period renews for one year, for Enterprise customers for 3 years. Microsoft is committed to provide full support for the product throughout your subscription.

We will continue to provide service allow adding more users and purchase of add-ons like email volumes throughout the subscription period. Microsoft will continue to support the product in that period fully, including the case of a hotfixes for observed issues. Yet we will eventually ramp down on the flow of monthly enhancements. We will instead fully focus our development on the new marketing app from Microsoft – “Dynamics 365 for Marketing, Business edition”. This new app will be available for Dynamics 365 customers in Spring release 2017. This will be an online release only in Spring 2017. Starting November 1, 2016, we have stopped selling Dynamics Marketing to new customers.

The spring release will focus on the topics of Customer engagement automation (campaigns), email and Web channels including content designer and templates, event management and event marketing, Integration and customer Intelligence including segmentation and analytics.

How will I in the future can move to the new generation of marketing tools from Microsoft: “Dynamics 365 for Marketing”?

If you are using the Dynamics CRM Connector for Dynamics Marketing today to connect Dynamics Marketing with your CRMOL instance today, you will find that the master data are already synchronized between the two systems. While you will find that you will need to reimplement campaigns and email messages with the new more powerful functionality in the new marketing app, you will also find that your audience and the lists you are syncing already today will continue to be in Dynamics 365 as well. We are looking at more tooling that help you with the transition.

Another option will be to continue using Dynamics Marketing running your existing customer engagement automation – some of which might have planned to run continuously for several months. By using the new app Dynamics 365 for Marketing, Business edition gradually more and more you will find the transition a smooth process.

What if I don’t want to transition to “Dynamics 365 for Marketing, Business edition”?

You may continue use the Dynamics Marketing until the end of your subscription (including the renewal you may be able to acquire, if you wish to do so.)

What happens to my data in Dynamics Marketing?

Upon the end of your subscription all customer data will be kept for maximum of 90 days. Before the subscription ends you may use the various functions for exporting data in Dynamics marketing to take a copy of records you like to take a hold of – if you need to do so.

Most objects provide an export to Excel function on the list representation. The OData endpoint together with Power Query and Excel is another good excellent tool to take a snapshot of relevant data in your Dynamics Marketing.

What about my product licenses, can I continue using them and when can I transition?

License plans will be available toward the Spring 2017 release.

from Microsoft Dynamics 365 Team blog http://bit.ly/2fJKBmR

Dynamics NAV 2017 as an App in Azure Management Portal

In Dynamics NAV 2017, you can use the Set Up Azure Management Portal guide to register Dynamics NAV in the Azure Management Portal and extract the information you need to use services such as the Sales and Inventory Forecast extension, Power BI, Office 365, and so on. The point of the registration is that Dynamics…

from Dynamics NAV Team Blog http://bit.ly/2fTGzZW

Get started with designing Dynamics 365 business apps by using App designer

Businesses today demand apps which are streamlined and focused on making their employees agile and productive.

There is a huge uptake in the demand for such apps but at the same time the app creation experience is challenged with the need for faster development and a high degree of technical skill. IT departments are overwhelmed and struggle to support these requests from business units.

Aimed at simplifying and democratizing the app development process, with the current release of Dynamics 365, we are introducing the Application Designer

App designer provides a visually rich and intuitive canvas for creating apps without writing a single line of code. The designer cuts across all persona boundaries and enables everyone to design and publish an app in minutes.

Integrated within the app designer is the brand-new WYSIWYG Site Map designer.

Putting things into action, business apps in Dynamics 365, namely Customer Service, Sales, Field Service and Project Service automation have been designed using the constructs and capabilities of App and Site Map designer.

So, welcome to App designer! Let’s acquaint ourselves with the key capabilities.

 

Creating business apps

It all starts from the My Apps page.

Use the Create App action to start providing meaningful information (properties) about your app, that users can easily associate with. To make this easy, all you need is the app name and the auto-defaults will take over. These defaults are shown upfront and you can choose to make edits/add details as necessary.

Promote your brand by adding icon for the app tile.

While you are at it, here are a couple of key properties to get you familiar with:

  • Name –  This is the name of your app
  • Unique Name –  The unique name defaults to app name and prefixed with the publisher prefix.
  • App URL Suffix – The suffix value defaults to the app name. You’ll see a preview of how the complete URL looks.

Once you have all the details, click Done to get started with the app designing experience.

 

Specify app properties in the Create a New App page

 

Designing apps using a visually rich and context driven canvas

 

The main stay of the app designing experience is the canvas. Onto the canvas as components are added, you will visually see the app composition taking shape.

With a few clicks and NO CODE, modify the composition, to meet the evolving needs of your business.

Let’s look at some of the key principles of the app designing experience.

  1. Universe of app components

The designing experience is supported using UX constructs, namely the following:

  • Sitemap
  • Dashboards
  • BPFs
  • Entities
    • Forms
    • Views
    • Charts

 

  1. Site Map configuration:

We have simplified the app designing experience such that all you need is to configure a Site Map for your app, using the WYSIWYG Site Map designer. This is a mandatory component, for the app to be successfully published for runtime access.

There are indications on the canvas and notification bar, in case the Site Map configuration is incomplete.

We will talk more about the Site Map designing experience and its capabilities in a forthcoming post.

 

  1. Adding components to your app:

The UX constructs are visually represented as Artifacts and Entity Assets tiles as part of the Components tab. Click on any of them to reveal a full list of their type.

For example, on accessing the Entities tile the UI flips to show existing entities listed by their Display and Unique name. To get to the entity of choice use the type ahead search and/or simply scroll and select the one you are looking for.

 

Select entities in the Components tab

 

The Add command option is another great way to get to the list of existing components and add to your app.

 

add-command-option

 

The designer retrieves all entities which are supported in solutions and are available as part of the Default solution of the backing Dynamics 365 CRM Org.

Should you need to create new components, for example a new dashboard, then simply select the Dashboard tile and click on Create New option to launch the dashboard designer.

 

Create New link in the Components tab

 

Tip: Using the ‘Add all Assets’ option, you can at one-go add all forms, views and charts for that entity as well.

 

Add all assets

 

  1. Working with app components added to the canvas.

Let’s continue with the example of entities… Once an entity is selected it is added as a row under the Entity View swim lane of the canvas. Asset tiles for that entity, i.e. form, view and charts are also now available.

Observe by default the tiles call out ‘All‘. This means that all forms, views and charts for that entity will be available to users in runtime (provided they have the required permissions). This is another example of simplifying and enabling rapid app designing.

 

All assets added to the entity

 

Should you have a need to select a specific set of entity assets then click on the relevant tile and pick the required assets from the components tab. On selecting 1 or more assets the tile shows the count of referenced assets (instead of All) and the flyout reveals the list of references.

 

Selected assets added to the entity

 

Dashboard and BPFs also follow the same pattern.

 

Tips:

  • We made sure that should you need more canvas space as you design large-complex apps, it is available as each swim lane can be collapsed and expanded, keeping you focused.
  • Form or view defaults are based on the defaults defined in the default solution of the organization. Should you need to have an app specific default, then only reference that form or view in the app.
  • Site Map designer provides an option to configure an app specific default dashboard.
  • Removing of referenced components is as straight forward as adding them. Select the relevant tile on the canvas and uncheck a referenced component.
  • To remove an entity and all its forms, view and charts in a single action, select the entity name tile on the canvas and click on the remove command action.

 

  1. Launching individual component designers

We spoke of how the Create New option is available for all app components and is a contextual way to create net new components as you design the app.

At the same time, you can also modify the definition of referenced components thru their designers. For example, to modify the definition of a referenced business process flow, click on the Open the Process Flow designer option to launch the new and reimagined process flow designer.

 

Open the designer for the referenced component to edit it

 

Our roadmap for future releases, looks to reimagine some of the legacy designers and have an inline experience to the app designer.

 

Validating your app to highlight errors and warnings

We wanted to make sure you have no surprises when you are ready to publish the app to your users and this where the Validate command action is useful.

Results of the validation are branched into two categories:

  1. Type error – Needs to be addressed before the app changes can be published.
  2. Type warning – Optional. Will not block app publish and impact runtime for app users.

 

Error and warning icons are contextually displayed against the app components tile present on the canvas. So, that you also have details on what to do next, the notification bar supports errors and warnings with a descriptive message as well.

 

Let’s now look at the most common types of errors and warnings one may experience, during app validation.

 

Error Warning
Site Map is not configured App does not reference at least one entity
An entity must have at least one form or view in the app.

 

Error and warnings on the notification bar

 

View details of errors and warnings

 

 

We also see the need for you to be aware of dependencies created when components are added to the app.  The validate action provides a warning category of highlight next to the canvas component tile creating these dependencies. At the same time the required tab provides a detailed listing, which is easy to correlate back to the canvas highlights.

Reviewing the dependencies and addressing them has been made easy, let’s understand how it works.

In this example, Customer Service Manager dashboard and the Case entity form are calling out several dependent components they need. These dependencies are neatly stacked and in a hierarchical and easy to understand format in the Required tab.

 

Canvas highlights Required tab
 Dependency warnings on the App Designer canvas  Dependencies on the Required tab

 

If you choose to not add 1 or more dependencies, you can simply hide them by clicking on Hide Dependencies. This doesn’t permanently ignore the dependencies from your app composition, but only hides them in the app designer until you click Validate or Get latest dependencies again.

Anytime a dependency is added to the app, it will be listed on the canvas under the appropriate component tile and the count of dependencies will change.

It’s fair to ask, what is the purpose of adding dependencies (which are warnings), when app runtime is not going to be impacted? The dependency addition experience ensures that should you choose to transport your app as a solution, for the app UX constructs your app universe is complete and ready to be imported in the target org.

We spoke about the solution support for apps on another post – Designing business apps – I.

Tip: Be sure to Save the app, before you run the validation.

Publishing your app and launching it for prime time

Now all that remains is to click the Publish command and have your app ready for your app users.

 

The app is publishing

 

Once you’ve published the app, go to the Published Apps tab on the My apps page. This will list the published app with the App tile, Name and description you’ve provided during the Create App step.

Publish action is only enabled when there are unpublished changes relevant to the app designer.

 

Business apps on the My Apps page

 

To view the runtime of the app, click anywhere on the tile.

Apps are role based and as an administrator, you can give access to desired roles for your app.

Tip: App properties were defined during the create app step. However, if you wish to change the app properties later, you can do this in the app designer from within the properties tab. Except Unique Name and App URL suffix, all other properties can be updated. Once done, save and then publish your app.

 

In conclusion

App Designer and Site Map designer will dramatically accelerate how business apps are built, reducing time to stand up apps from days to minutes and empowering a new category of app creators.

 

Additional Resources

 

Business apps in Dynamics 365

Where to find your business apps

Design custom business apps by using the app designer

Manage access to apps with security roles

Designing Business Apps – I

 

from Microsoft Dynamics 365 Team blog http://bit.ly/2fS2XR2

Designing Business Apps – I

Applies to Dynamics 365 Online

With the current release of Dynamics 365, we are introducing the concept of tailored, purpose-built apps for business functions. Our view is that these apps will simplify the consumption experience by showing functionality and components that are relevant to the users.

When we had set out to bring about the business apps functionality, we decided to have the following key goals:

  • To simplify the current experience and UI
  • To provide a way to create purpose-built apps that address a specific task, are built for a persona,  or just to modularize the monolithic interface.
  • And finally, to make it easy to build such business apps.

And we now have the first release of the business apps framework that you can get started on. This blog will deep dive into the realization of the concept and how it manifests in the application.

Following are the key tenets of the business apps framework:

Business Apps are available via a new Solution aware component called Apps.

 

Apps node in the Solution explorer

 

All Microsoft and custom built apps will be visible in this area. An App can be packaged inside a solution, exported and imported just like any other solution component.

 

An App stores references to UX artifacts only, namely the following: 
  • Sitemap
  • Forms
  • Dashboards
  • Views
  • Charts
  • BPFs

This implies that a custom App can be created just by composing one or more of the above mentioned UX components.

E.g. In a simple Ticket management app, you can bundle in just the required set of Customer Service dashboards, some views of the Case entity and a relevant Case form. While users will have access to other entities, forms, views etc. based on their overall security privileges, when in the context of that app, they will see the chosen components only.

 

Did we say App can reference a Sitemap?

Yes, each app will have its own Sitemap. The App’s Sitemap defines the navigation of the app. So in the case of a simple Ticket management app, you may choose to have just two sub areas pointing to Dashboard and Case view.

Below is a sample Sitemap of the Service app.

 

Site map of the Customer Service app

 

All Sitemaps are visible in the Client Extension node in the Solutions area. The full application continues to have the same default Sitemap.

 

What references does an App need to work?

Just the Sitemap. In line with the simplification goal, an App is ready to run once the navigation has been defined i.e. the Sitemap has been referenced. At runtime, the app will show components that the user has got access to. And as the admin refines the App to reference explicit UX components in the App, only the referenced components will start to show in runtime for users.

 

And, how are Business Apps created? 

Apps can be created and composed using the new App designer. Using the App Designer will be covered in the next post.

 

App designer

 

And, since an App requires a site map, we now also have a fully integrated Site map designer! More on that in the next post.

 

Site map designer

 

Accessing the App

Apps are role based and as an administrator, you can give access to desired roles to the app.

 

Assign roles in the Manage App dialog box

 

Once users are given access, they can access the apps from any of the following areas:

 

  • The new My Apps page

This page can be accessed via Settings > Applications > My Apps. Or directly by typing <URL>/apps

My Apps page

  • The new App Switcher

Drop down the Dynamics 365 menu to access the App Switcher. With this, users can switch between apps even when they are working on another one. Infact the App switcher lists apps across Dynamics 365 including Power Apps. An introduction here to the new App Switcher and Dynamics 365 home. App switcher is only available for Dynamics 365 online.

App Switcher

  • Directly through the App URL

Each App can have its own URL. As an administrator, you can choose a friendly URL for an app e.g. ticketlite for the simple Ticket Management app. Once set, any user can directly access the app via:

<URL>/apps/ticketlite i.e. http://bit.ly/2fDtZdw

Current Support for Apps

As of current release, Business App supports web client only. We will update this blog as new client support is announced.

 

Additional Resources

Business apps in Dynamics 365

Where to find your business apps

Design custom business apps by using the app designer

Manage access to apps with security roles

 

 

– Prateek Sethi

 

 

from Microsoft Dynamics 365 Team blog http://bit.ly/2eLiJxS

Using Resco MobileCRM Woodford Solution for Configuring Field Service Mobile App

I was recently working on a Field Service functionality demo, where I had to demonstrate the Field Service mobile app, with additional Field Service entities like Work Orders, Agreements and Bookable Resources to be set up using the mobile device.

As we needed the Resco MobileCRM Woodford Solution to be deployed in CRM Online, I downloaded the trial solution from the link below.

http://bit.ly/2ePAg5Q

Once downloading and installing this Solution for Dynamics CRM 2016 Online Update 1, I tried to go to Settings >> MobileCRM >> Woodford and access the MobileCRM Woodford setting.

It immediately promoted me with an error as shown below.

2016-11-08_034905

Ideally the system should prompt you with a screenshot to increase the isolated storage for Silverlight as shown below.

increase-quota

However, I was getting the same error message irrespective of the browser used.

On doing some troubleshooting, I was running the browser in InPrivate mode and I realized that this setting was causing the issue.

I tried to run the browser in the normal mode, and I was able to set the isolated storage setting properly and go ahead with configuring the Field Service Mobile app using the settings as explained in the article below.

http://bit.ly/2egsWnm

Hope this helps.

from Dynamics PTS Team Blog http://bit.ly/2ePAr0H

%d bloggers like this: