Page 322 of 693« First...102030...320321322323324...330340350...Last »

Collection Letters do not display in all windows in Collections Management for Microsoft Dynamics GP

There are 25 out of the box collection letters available in Collections Management in Report Writer, but certain letters only display in certain windows in Collections Management. Tweny of these predefined letters are only available in the Collection Main window to be printed for one customer at a time, and the remaining five of these canned letters are available in the Query Letters window for a mass mailing.
This is the current design. The 25 predefined letters in Collections Management can only be printed in these windows:

The following 20 predefined Collection Letters from Report Writer can only be printed for one customer at a time in the Collection Main window:
CN_Letter01 through CN_Letter10
CN_AddressID through CN_AddressID10

The following 5 predefined Collection Letters from Report Writer with the mail-merge features can only be printed for mass customers in the Query Letters window:
CN_Mail_Merge01 through CN_Mail_Merge05


Note: There are no options to be able to get these 25 predefined letters from Report Writer to show in other Collections windows than they currently are available in. See the Resolution below for an alternative solution.

The alternative solution is to create your own custom collection letter in Microsoft Dynamics GP. Collection Letters that you create in the Collections Management Letter Maintenance window can be seen in both the Collection Main window to print for one customer at a time, and also in the Query Letters window for mass mailing.  

To access the Collections Management Letter Maintenance window to design your own collection letter, follow these steps:

1. Click on Cards, point to Sales, and click on Collection Letters.

2. Name the Letter, and provide a description.

3. Leave the Hide in Lookups checkbox blank.  However, if you wish for this Letter ID to be hidden in Lookup windows in the Print Selection and Query Letters window, then mark this option. 

4. Set a default Action ID if desired.

5. Enter a Default Subject, if you will be sending the letter out via email. Otherwise, leave it blank.

6. You can create the letter within the window below, or using Microsoft Word. Only check the Microsoft Word Document checkbox if you wish to create the letter in Microsoft Word instead (to add logos, etc and use other functionality from Microsoft Word). Otherwise, leave this checkbox blank if you want to create the letter in Microsoft Dynamics GP. Letters created using either of these methods will be available in all Collections Management windows for printing.

For more information on how to create a collection letter using the Microsoft Word functionality, click the following article number 949761 to view the article in the Microsoft Knowledge Base:  

949761 

(http://support.microsoft.com/kb/ 949761/
)
How to create a new collection letter in Word

7. Start to type the letter in the large text box in the bottom of the Collection Letter Maintenance window. For any functions, place your cursor where you want the function to be added in the text body and then click Insert to insert the function into the body of the letter.

For example, you can type “Dear” and then put your cursor after it. Select the Function for Customer Info, and Contact Name, and click Insert. So when you print your letters, it will merge with the Contact Name set up on the Customer Maintenance to personalize each collection letter.

Note: The functions must be inserted into the body of the letter using the Insert button. Do not hand-key or copy and paste the functions within the letter.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Visit site:
Collection Letters do not display in all windows in Collections Management for Microsoft Dynamics GP

Error message when you try to synchronize a Dynamics CRM 4.0 client to Outlook: "An unknown error occurred while synchronizing data to Outlook"

You may receive the following error message when you try to synchronize Microsoft Outlook with a Microsoft Dynamics CRM 4.0 Citrix client:

An unknown error occurred while synchronizing data to Outlook.

This issue occurs because, by default, Microsoft SQL Server CE does not support mapped drives.

Note SQL Server CE requires UNC paths.

To resolve this issue, follow these steps:
  1. Install Microsoft Dynamics CRM 4.0 Update Rollup 20. For more information about how to download and install Microsoft Dynamics CRM 4.0 Update Rollup 20, visit the following Microsoft website:
  2. Update the environment configuration settings in the Microsoft.crm.se.orgdborgsettingstool.exe.xml file.

    Note By default, the Microsoft.crm.se.orgdborgsettingstool.exe.xml file is located in the following folder:

    Program FilesMicrosoft Dynamics CRMServerbinTools

  3. Update the ClientExpandPathsToUNC database setting by using the Microsoft.crm.se.orgdborgsettingstool.exe tool. To do this, follow these steps:
    1. Start the Microsoft.crm.se.orgdborgsettingstool.exe tool.

      Note By default, the Microsoft.crm.se.orgdborgsettingstool.exe file is located in the following folder:

      Program FilesMicrosoft Dynamics CRMServerbinTools

    2. Type the following command, and then press Enter:

      microsoft.crm.se.orgdborgsettingstool update crm_organization ClientExpandPathsToUNC TRUE

      Note In this command, the crm_organization placeholder is the name of your organization.

  4. Verify the updated setting. To do this, type the following command, and then press Enter:

    microsoft.crm.se.orgdborgsettingstool retrieve

For more information about the Microsoft.crm.se.orgdborgsettingstool.exe tool, see the following article in the Microsoft Knowledge Base:
2479288 

(http://support.microsoft.com/kb/2479288/en-us/
)
A new tool that retrieves and changes the Organization level settings in Microsoft Dynamics CRM 4.0 configurations is available

Read More:
Error message when you try to synchronize a Dynamics CRM 4.0 client to Outlook: "An unknown error occurred while synchronizing data to Outlook"

InstallPSTAction failed Error When Installing Dynamics CRM Client for Microsoft Office Outlook

After uninstalling Dynamics CRM 2011 Client for Microsoft Office Outlook and installing the Dynamics CRM 4.0 Client for Microsoft Office Outlook, you get the following error when trying to run the configuration wizard.

Error| Configuration exception.System.Exception: Action Microsoft.Crm.Config.Client.InstallPstAction failed. —> System.Runtime.InteropServices.COMException (0x8004010F): LaunchOutlookInstallerProcess failed.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Crm.Config.Client.InstallPstAction.Do(IDictionary parameters)
at Microsoft.Crm.Setup.Common.Action.ExecuteAction(Action action, IDictionary parameters, Boolean undo)

This is due to the uninstall leaving the CRMForOutlookInstaller.exe file in the C:Program FilesMicrosoft Dynamics CRMClientConfigWizard directory.
To resolve this issue:

1. Navigate to C:Program FilesMicrosoft Dynamics CRMClientConfigWizard directory or C:Program Files (x86)Microsoft Dynamics CRMClientConfigWizard directory.

2. Delete the CRMForOutlookInstaller.exe file.

3. Do one of the following options:

  • Replace the CRMForOutlookInstaller.exe from the 4.0 client install bits.
  • Run a repair on the Dynamics CRM 4.0 Client for Microsoft Office Outlook installation.
  • Uninstall and reinstall the CRM 4.0 Client.

4. Run the Configuration Wizard.

The CRMForOutlookInstaller.exe is left behind in order to remove the per-user registry keys from any other users that may have configured the Dynamics CRM Client.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

View post:
InstallPSTAction failed Error When Installing Dynamics CRM Client for Microsoft Office Outlook

The folders you are trying to change do not support this operation

This issue can occur if you follow steps similar to these:

1. In the Dynamics CRM Client for Outlook, right click on a CRM record (For example Contact).

2. Choose Follow Up to add an Outlook Follow Up item to the ToDo Bar.

3. Next, switch to another Entity like Accounts or Opportunities. 

4. Attempt to delete the Follow Up item from the ToDo Bar. 

The following error will occur:

“The folders you are trying to change do not support this operation.  Could not complete the operation because the service provider does not support it.”

MAPI event listeners only listen to the folder events for the current grid that is displayed. If you switch to a different entity (account) and you are trying to delete a contact you will get this error.
This is by design as the MAPI event listener does not listen on all folders for performance reasons. If you want to delete a record from the ToDo bar in Outlook you need to switch to that entity type.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

See the article here:
The folders you are trying to change do not support this operation

Unable to configure the Microsoft Dynamics CRM E-mail Router

Unable to configure the Microsoft Dynamics CRM E-mail Router against an OnPremise deployment. The following error is returned:

The E-mail Router Configuration Manager was unable to retrieve user and queue information form the Microsoft Dynamics CRM server. This may indicate that the Microsoft Dynamics CRM server is busy. Verify that URL ‘http://crmservername/orgname’ is correct. Additionally, this problem can occur if specified access credentials are insufficent.  To try again, click Load Data. (The provided uri did not return any Service Endpoints!)

Microsoft Dynamics CRM 2011 utilizes WCF endpoints for client communications. The WCF endpoints cannot support more than 1 binding per Protocol. 

If the CRM website has more than one http or more than one https binding,  the E-mail Router will fail to configure. 

Open IIS Manager and limit the CRM Website to 1 http and (or) 1 https binding.   
  1. Click Start, click Run and Type in inetmgr.
  2. Expand Sites and click on the Microsoft Dynamics CRM website.
  3. In the Actions Pane click on Bindings.
  4. In the Site Bindings window ensure that you only have one http and/or only have one https binding type. If you have multiple http and/or multiple https bindings they need to be removed.

Note: The binding that should remain is the binding that is defined in the Deployment Manager. To check the urls open Deployment Manager, right-click on Microsoft Dynamics CRM and choose Properties, click the Web Address tab. 

Note: If IFD is used the Certificate matching your IFD settings should be kept.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Read More:
Unable to configure the Microsoft Dynamics CRM E-mail Router

No Organization Appear When Configuring the Microsoft Dynamics CRM Client for Microsoft Office Outlook

When running the configuration for the Microsoft Dynamics CRM Client for Microsoft Office Outlook no organizations appear in the list.
If you are connecting to Dynamics CRM Online and no organizations appear in the drop down it could be due to not accepting the Dynamics CRM Online invitation that was sent to you when you were created as a Dynamics CRM Online user.
To resolve this issue. Login to the Microsoft Dynamics CRM Online organization using the web client. If you have an active invitation for the organization then it will take you through the wizard to accept the invitation. Then try to configure the Outlook client again.

If your invitation has expired then a Dynamics CRM user in your organization with the rights to send invites would need to send you another invite.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Read More:
No Organization Appear When Configuring the Microsoft Dynamics CRM Client for Microsoft Office Outlook

The Microsoft Dynamics Adapter does not update the price level on the line items in Microsoft Dynamics GP 10.0

Consider the following scenario.  You install the Microsoft Dynamics Adapter to integrate data from Microsoft Dynamics CRM 4.0 to Microsoft Dynamics GP 10.0.  You activate the Order to Sales Order map.  You enter an order in Microsoft Dynamics CRM 4.0. 
The corresponding sales order in Microsoft Dynamics GP 10.0 does not have a price level applied to the line items.

The Order to Sales Order map is setup to apply the Microsoft Dynamics CRM 4.0 price list which is on the order header to the GP 10.0 sales order header instead of the line items.

Update the Order to Sales Order map with the following steps:

  1. Open the Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP 10.0.
  2. Expand Maps, and then click Order to Sales Order.
  3. In the Order to Sales Order map expand Sales Order, expand Sales Order Lines, expand Item, and then expand Price LevelID.
  4. Edit the map in the Price Level ID field with the following:

=Trim(If(Contains(Price ListDynamics Integration Key, “(“), Mid(Price ListDynamics Integration Key, 1, FindString(Price ListDynamics Integration Key, 1, “(“)), Price ListDynamics Integration Key))

Remove the map to the incorrect field with the following steps:

  1. Open the Microsoft Dynamics CRM Adapter for Microsoft Dynamics GP 10.0.
  2. Expand Maps, and then click Order to Sales Order.
  3. In the Order to Sales Order map expand Sales Order, and then expand PriceLevelID.
  4. Delete the map in the PriceLevelID.
  5. Click the Activate button if the map is not active, and then click Save.
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Read More:
The Microsoft Dynamics Adapter does not update the price level on the line items in Microsoft Dynamics GP 10.0

"The journal entry is not accessible." displays in the Journal Entry Inquiry window in Microsoft Dynamics GP

When trying to view a journal entry in the Journal Entry Inquiry window, this message displays:  “The journal entry is not accessible.”
There are several reasons on why this message may happen:

1. A 3rd party product is interferring- see Method #1 in the Resolution section.

2. The transaction for the journal entry has been removed from the GL table – see Method #2 in the Resolution section below.

3. For any other reason, open a support case for further assistance and attach the Dexsql.log in Method #3. 

Below are possible explanations on why the Journal Entry (JE) may not be accessible to view:

Method #1: A 3rd party product may cause the journal entry not to display. To test, follow these steps:

1. On the Microsoft Dynamics GP menu, point to Tools, point to Customize and click on Customization Status.

2. Click on any 3rd party product and then click Disable. (You can leave “Microsoft Dynamics GP” enabled, but can disable all others. Although any other Microsoft products should compatible.) Disable any 3rd party products that you recognize.

3. Exit out of the window.

4. Now test pulling up the Journal entry again. (You may need to go back and click on Enable for a few modules and keep testing, until you find the module that is causing the problem.)

NOTE: Disabling modules in the Customization Status window is temporary. Therefore, if you exit out of Microsoft Dynamics GP and log back in, all the products will automatically become enabled again. 

——————————————————————————————————————————————————————-

Method #2: Check if the transaction does exist in the General Ledger (GL) tables. If it is missing from the open table, this would explain why it doesn’t pull up. To do this, follow these steps:

1. Open SQL Server Management Studio.

2. Click on “New Query” in the top menubar.

3. Select the company database from the drop-down list.

4. Copy in these scripts to look for the transaction in the GL Year-to_Date transaction Open table (GL20000) or the GL Account Transaction History table (GL30000). Execute these scripts against the company database to locate where the Journal Entry resides.

Select * from GL20000 where JRNENTRY = ‘xxx’ (insert in the JE# for the xxx placeholder)
Select * from GL30000 where JRNENTRY = ‘xxx’ (insert in the JE# for the xxx placeholder)

NOTE: You should get at least two lines returned from the open table: each journal entry will have at least one debit and one credit record. If you don’t get any results returned, then the journal entry has been removed from the GL table which would explain why you are not able to view it.

NOTE: The Journal Entry Inquiry window is designed to pull from the open table. So if you find it in the history table, you would not be able to view it using the Journal Entry Inquiry window. You can only view historical journal entries using Smartlist.

————————————————————————————————————————————————————

Method #3: For any other reason, turn on a dexsql.log of trying to view the journal entry and open a new chargeable support case for further assistance. To turn on the dexsql.log, follow the steps in KB 850996.

1. Turn on the dexsql.log using the steps in KB 850996. The link is:

https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;850996

2. Log into Microsoft Dynamics GP and click on Inquiry, point to Financial and click on Journal Entry Inquiry.

3. Type in the Journal Entry number and stop.

4. Delete the dexsql.log that was created up into this point in the GP code folder, as we don’t need any data in the log up to this point.

5. Back in the Journal Entry Inquiry widnow, click OK to reproduce the message. Stop there.

6. Flip over to the GP code folder and immediately rename the dexsql.log that was created, so you do not write anything else you do in GP to this log.

7. Open a support case and attach the dexsql.log to the case for review.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Link:
"The journal entry is not accessible." displays in the Journal Entry Inquiry window in Microsoft Dynamics GP

Query not pulling in all customers with balances in Collection Management using Microsoft Dynamics GP

If you build a query in Collections Management, you may notice that all customers with overdue balances are not pulling into the query. Even if you filter only on Customer ID, the query still does not pull in a particular customer that has an overdue balance.
The “Statement To” Address ID is blank on the Customer Maintenance card in Receivables Management. 
Fill in the “Statement To” Address ID on the Customer Maintenance card and then the customer will pull into the query in Collections Management. To do this, follow these steps:

1. On the Cards menu, point to Sales, and click on Customer.

2. Select an Address ID for the Statement To field.

3. Save.

4. Test the query again and now this customer will pull in. To build a query, click on Transactions, point to Sales and click on Build Query. Select the query filters as desired, and click on Query.

In SQL, the “Statement To” Address ID is stored in the STADDRCD field in the RM Customer MSTR table (RM00101). You can run the below script against the company database in a query window in SQL Server Management Studio to view all the active customers that are missing an address ID in this field:

select * from RM00101 where STADDRCD = ” and INACTIVE = 0 

After identifying the active customers that have a blank Statement To Address ID, then use the steps in the Resolution section above to select an appropriate Address Id in the Statement To field for each customer. 

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

See more here:
Query not pulling in all customers with balances in Collection Management using Microsoft Dynamics GP

When you Launch Business Portal 5.1 for Microsoft Dynamics GP 2010 after a Reinstall, the Error "Service Unavailable" May Appear

Consider the following scenerio: Business Portal 5.1 for Microsoft Dynamics GP 2010 is uninstalled without removing the SQL objects. Business Portal 5.1 for Microsoft Dynamics GP 2010 is then reinstalled. When Business Portal 5.1 is launched, the error ”Service Unavailable” may appear.
The Application Pool used by Business Portal 5.1 has stopped due to missing credentials.
1. Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Central Administration.
2. Click Security.
3. In the General Security area, click Configure managed accounts.
4. Find the domain account that owns the Business Portal Application Pool and click on the Edit icon.
5. In the Credential Management section, click to select the Change password now checkbox and click to select the Use existing password radio button.
6. Enter the password for the domain user who is listed.
7. Click the OK button
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations.

Continued here:
When you Launch Business Portal 5.1 for Microsoft Dynamics GP 2010 after a Reinstall, the Error "Service Unavailable" May Appear

Page 322 of 693« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories