Over the past couple of years, Dynamics 365 has become a much broader application. As such, Microsoft introduced various apps to help organizations focus on the areas they need to utilize for their business. Examples of these include the Dynamics 365 for Sales app and the Dynamics 365 for Service app.However, many organizations need a way to have a custom app that allows their users to see and access the specific areas of Dynamics 365 they need. This is where the App Designer comes in.
The App Designer allows you to create a new custom app and add in the entities that you need for your organization. So, let’s look at how to design a custom app using the App Designer.
First, you will need to navigate to the App Designer. On a side note, accessing the App Designer has changed over the past couple of updates.
To access the App Designer, you will first need to know which method your organization uses to configure Dynamics 365. There are two methods for this.
After using one of the above methods, you will see a screen like this with the Dynamics 365 Components listed on the left-hand side.
You will need to click on “Apps” from the menu. Now, depending on the Dynamics 365 Subscription(s) you purchased, you may see some or all the apps listed as in the below screen shot. Next, click the “New” button.
After clicking the “New” button, you will see the App Designer window appear.
Now that the App Designer window is open, you will enter information and choose different options that will determine how this custom app will appear and behave.
Let’s walk through the fields to help you understand each one.
For this example, I will keep the default options set.
Lastly, click “Done” in the top right corner. This will launch the App Designer window.
First, a Site Map needs to be created. Click on arrow to the right of “Site Map” at the top of the screen. This will display the “Site Map” designer.
This layout may be familiar to you. This is the Navigation menu layout that you see within Dynamics 365.
First, click on the “New Area” tile. This will allow you to change the text. To keep things simple for this example, I have named the area “Sales and Service” as we did in the App Designer start screen above.
Second, click on “New Group” to change the name of the group.
Third, click on “New Subarea” to edit this subarea.
On the right-hand side, select the options that you would like. For this example, I will be choosing various entities.
After you have added your first Subarea, be sure to click “Save” to save your updates.
Continue adding the entities you would like to display until you feel you are finished. Additionally, you can add other Groups with Subareas. To add a new Group or Subarea, click the “+Add” button at the top-left.
Once you are satisfied with the options, be sure to click “Save” (unless you have already done this), and then click “Publish”. However, this will only publish the SiteMap and not the Custom App.
First, click on “App Designer” in the top-left to return to the app designer screen.
This will display all the entities you chose in the SiteMap Designer. Notice in the top-right that this app is still in “Draft”. You will need to click “Save”, then click “Publish”.
Next, after the custom app is published, go back to the solution file and you will see your newly created app in the Apps list.
Finally, you should see the new app tile on your Dynamics 365 home page: https://home.dynamics.com/
Lastly, you will need to test the navigation. Click on the tile from the Dynamics 365 Home Page. This will take you to the new app URL. Click on the navigation menu to see if your options appear.
You can now save this URL in your browser bookmarks for easy access.
As you can see, creating a custom app for your organization is not difficult. If you would like to try this out, I would suggest using a Sandbox instance, or create a 30-day trial of Dynamics 365.
Aaron Back is Microsoft Certified Professional with many years experience with Microsoft Dynamics 365 (CRM). He is actively involved with the Microsoft Dynamics CRMUG (User Group) Community. His involvement includes: Serving as Chapter Leader for his local CRMUG Chapter, serving on the CRMUG Board of Advisors, and speaking at the annual CRMUG Summit conference.
For more information or assistance with Dynamics 365 (CRM) contact ACE!
The post Designing a Custom App for Dynamics 365 appeared first on CRM Software Blog | Dynamics 365.
You have a well-designed CRM Word-Templates for Invoices, Price Quotations or Contracts, and you now wish to Email the generated document from the Word-Template, as PDF file attached to an Email to a client.
If you don’t have Dynamics PDF-Docs, this is a process that can take you considerable time, especially if you are generating many such documents in Dynamics CRM / Dynamics 365.
With Dynamics PDF-Docs its is as simple as 1-2 (not even 1-2-3)
From the record page – Click the “PDF-Docs” button>Select the Word Template> and select any one of eight different options to Download as PDF, Save to Note, Attach to Email or Upload to SharePoint, and you are done.
With Workflow – Automate this process with a workflow, triggered when a workflow condition is met or run the workflow on demand, from your tablet or even an iPhone.
Dynamics PDF-Docs price is US$690 only per CRM Organization (one-off payment).
Price includes FREE lifetime version upgrade and free Email support.
With Dynamics PDF-Docs you always have the most updated version, by importing the trial version on our website (and using the Product Key provided upon purchasing the product).
Dynamics PDF-Docs free trial version can be loaded from this URL
Try it only takes 2 minutes to install, and 2 clicks to try with CRM out-of-box Word Templates.
If you do not have Word Templates, why not use our FREE CRM Word-Templates and redesign then the way you like it. Click here to download free CRM Word Templates
The post On Click to PDF Word Template and Attach to Email appeared first on CRM Software Blog | Dynamics 365.
Trying to decide whether to implement Microsoft Dynamics CRM or SalesForce may seem like a tricky decision at first. We are here to guide you through your decision-making process and present some advice our clients have found helpful in the past.
Logan Consulting is a proud supporter of Dynamics CRM, also known as Dynamics 365, for a variety of reasons. Dynamics 365’s overall cost, integration ability, development, deployment, and consulting options outshine the competitors.
The post Microsoft Dynamics 365 vs. SalesForce appeared first on CRM Software Blog | Dynamics 365.
Normally we hear about all the great new features being added to Microsoft Dynamics 365. But you also need to be aware of the features and capabilities that are being deprecated
Technically "to deprecate" means "to express disapproval of (something)". In the software world, it means something that is “usable but regarded as obsolete and best avoided, typically because it has been superseded.”
According to Microsoft deprecated means “we intend to remove the feature or capability from a future major release of Dynamics 365.” However, the feature or capability will continue to work and is fully supported until it is officially removed.
It is important for all Dynamics 365 users to be aware of which features are on the chopping block so that they can determine if it will impact their business and decide on the best strategy before their next upgrade.
In this article, Microsoft discusses 13 deprecated features that apply to Dynamics 365 Customer Engagement as of version 9. Customer Engagement refers to the applications that make up the CRM portion of Dynamics 365: Sales, Customer Service, Field Service, and Project Service Automation applications.
When the Crowe CRM team looked at this list, we spotted a few we felt would be most likely to impact our Dynamics CRM and Dynamics 365 clients during their next upgrades and would require additional planning.
But it’s not all bad news. Microsoft is continually adding new functionality. Two new features that our team is excited about are:
These new features may sound simple, but they will be huge time savers for some organizations.
When features are removed, it is usually because there is now a better way to accomplish the same result. Microsoft gives recommendations for the functionally set to replace anything that is being deprecated. Working with a knowledgeable Microsoft Dynamics 365 partner, such as Crowe Horwath, means this planning will be done before your next upgrade.
If you are interested in discussing an upgrade plan for Microsoft Dynamics 365 (formerly Microsoft Dynamics CRM) contact us today.
Ask about our offer “Moving CRM to Dynamics 365: 3-Hr Assessment” if you are interested in moving to the Dynamics 365 cloud.
By Ryan Plourde, Crowe Horwath, a Microsoft Dynamics 365 Gold Partner www.CroweCRM.com
Follow us on Twitter: @CroweCRM
The post 13 Features Being Removed From Future Releases of Dynamics 365 appeared first on CRM Software Blog | Dynamics 365.
With Dynamics SharePoint Organizer (SPO) each CRM entity is configured how the entity integrates with the corresponding SharePoint Document Library. Naturally, each CRM entity has different type of documents and different tags (metadata) that describes the type and content of the document, what the document is about, and how it relates to other documents and other related parties in and outside the organization. When document is generated in CRM entity, it is linked to a record as attachment to Notes, and as attachment to Email activity. The record has attributes / fields to describe the record and documents related to it. A record of an Invoice entity has the Invoice document attached to Notes or attached to incoming Email sent from the accounting department. The record has fields that describe the Invoice document such as invoice number, total amount, due date, invoice description, and the Account that was issued with this invoice. When invoice document is uploaded to SharePoint, the SharePoint columns are updated with these fields, which are called metadata. Metadata is crucial to filter documents in a Document Library View, and improve the relevance of SharePoint search results.
One entity may have many documents, and the documents can be grouped into Document Types. As an example, an organization managing projects with customised entity Projects, may have documents of the types: Project SOW, Project Milestones, Invoices, and Payments. SharePoint document library is configured to accept these four types of documents, created in the Project Entity in CRM. Dynamics SPO can be configured, for the Project Entity, to match the document in CRM with the corresponding Document Type in SharePoint. Categorizing documents by their types enhance SharePoint navigation. The corresponding projects document library stores all project’s documents in one library, and displays the list of documents based on selected document type.
Dynamics SPO can configure the SharePoint folder structure where documents are uploaded. There are 3 different approaches to SharePoint folders structure:
Single Folder Structure – in this configuration all documents related to an entity are uploaded into a selected folder. Each entity can be configured to upload to a related folder in SharePoint, Orders are uploaded to a folder called Orders, Invoices to Invoice Folder, and Payments to the Payments folder.
Alternatively, two or more entities are configured to upload to one selected folder, let’s say “Commercial” folder. In this case Orders, Invoices, and Payments documents are all uploaded to “Commercial” folder. Note that in addition to selecting the folder to upload the documents, tagging them with Document Types like Orders, Invoices, and payments, will filter the required documents, although all documents are in one single folder.
Child / Parent Folder structure – When two CRM entities are related to each other, like Invoices are related to Accounts, Dynamics SPO will create new folder when an invoice is uploaded for an Account folder not yet created in SharePoint. In this structure it firstly lists all Accounts as folder names, the Parent Folder and when a folder of an Account is opened, the documents of this account are listed in the Child Folder.
CRM Out Of Box Structure - The third option in Dynamics SPO is for customers already using CRM out-of-box (OOB) integration with SharePoint, and wishing to keep the existing folder structure which already is in use to upload documents to SharePoint. While Dynamics SPO will follow the CRM OOB integration with SharePoint, other features like Document types and metadata are available even for those existing folders.
No doubt that using SPO functionality to upload documents to SharePoint is far more efficient and time saving than the one offered with CRM OOB integration with SharePoint.
Incredible offer for Dynamics SharePoint Organizer (SPO) users
For limited time only, customers purchasing Dynamics SPO will receive FREE online hand on training configuring any 2 CRM entities to upload documents to SharePoint. Dynamics SPO is available to download as trial version. We provide unlimited 30 day extended trial periods, and FREE email support and advice on best practises configuring Dynamics SPO for your organization.
Click here to Download Trial Version
The post Incredible offer for Dynamics SharePoint Organizer (SPO) users appeared first on CRM Software Blog | Dynamics 365.
No related posts.