Blogs

Copy an existing workflow in Dynamics CRM 2011/2013

Being able to copy a workflow in your CRM system can be advantageous in saving you time if you need to create a workflow similar to an already existing workflow or perhaps you want to make changes to a complex workflow but do not want to risk losing your original work. To copy an existing workflow, follow the steps below:

1. Make sure the workflow is in draft mode. If it is currently activated, select the activated workflow, click "Deactivate". Note: If you do not have ownership of the workflow, you will need to do this before you can deactivate. To take ownership, select the workflow, click the assign button on the top menu, select "assign to me".

2. Once in draft mode, open up the workflow record. Where it says "Activate As", use the drop-down list to select "Process Template". Save. Activate. The workflow will now appear under the "All Process Templates" view.

3. To create your new copy, click "New" (Create a new process), fill in required fields, and under Type select "New Process from an existing template". Select your template.

This also applies to Actions and Dialogs in CRM 2013. To copy a Business Process Flow in CRM 2013, simply open the existing Business Process Flow record, click Save As, and your copy will appear.

Take Control of your "Control Acounts"

Over the years I have seen accounting departments continually spend time reconciling their sub-ledgers (Accounts Payable and Accounts Receivable) to their respective GL control accounts. Inevitably the reasons for these differences arise from individuals erroneously keying these accounts on AP and AR transactions. Or, general journal entries being recorded to those same control accounts creating variances with their respective sub-ledgers.

A very simple way of exercising more control over the types of transactions posting to these GL accounts is to uncheck the “Allow Account Entry” box in the GL Account Maintenance window (Cards>Financial>Account). Unchecking this box prohibits any user from manually entering this account on a transaction. The control accounts are populated automatically from the Company posting setup or applicable master records (Cards), thereby eliminating user errors and increasing the chance of clean reconciliations.

Dynamics CRM directs to mobile version

If you are using Internet Explorer 10 or 11 and trying to access Microsoft Dynamics CRM but keep getting a page that looks like a mobile version, you probably need to run your browser in Compatibility Mode. Please reference one of our previous posts on how to put Internet Explorer into Compatibility Mode using the following link: http://njevity.com/blog/internet-explorer-10-compatibility-mode

Grant Microsoft Dynamics GP Users Rights to Administer User Account & Access

We recently were working with a Dynamics GP client that has hundreds of users. They needed to give their IT department the ability to administer GP users and user access without giving them the DYNSA password. We found no documentation on how to accomplish this. So by trial and error we came up with a solution:

IN DYNAMICS GP (login as 'sa'):
Created new Security Task: ADMIN_SYSTEM_USER
Gave the Task access to:
Category: System
Product: Microsoft Dynamics
Type: Windows
Series: System
- Activity Tracking Setup
- Alternate/Modified Forms and Reports
- Remove Security Setup Records
- User Access Setup
- User Class Setup
- User Security Setup
- User Setup

Created new Security Role: USER_ADMIN and added DEFAULT and ADMIN_SYSTEM_USER tasks to it.

Added Role to users security in GP

IN SQL SERVER MANAGEMENT STUDIO:
From Security:
Added the following roles to SQL user accounts
dbcreater
securityadmin

Added the following mapping to the SQL User accounts for all GP DBs .
db_owner
db_securityadmin
DYNGRP
public

Dynamics GP DYNSA cannot grant users access to companies or company

We recently had an issue where DYNSA could not grant users access to companies. The User Access Screen would not allow DYNSA to check or uncheck access to any company. We found that DYNSA was not the owner of one of the company databases.

Make sure DYNSA is the owner of the DYNAMICS system database and all Company databases. Run:
EXEC sp_changedbowner 'DYNSA'
against EACH GP database.

Syndicate content