Page 22 of 982« First...10...2021222324...304050...Last »

You cannot import the customizations from a Microsoft Dynamics CRM 4.0 system that you upgraded to another Microsoft Dynamics CRM 4.0 system that you also upgraded

Consider the following scenario. On a Microsoft Dynamics CRM 3.0 system, you create a custom entity. You
export the
customizations of
this custom entity, and you import the customizations on another Microsoft Dynamics CRM 3.0 system. Then, you update both systems to
Microsoft Dynamics CRM 4.0. Next, you update the custom entity on one
of the Microsoft Dynamics CRM 4.0 systems. Finally, you try to export the
customizations from this Microsoft Dynamics CRM 4.0 system, and you try to import the
customizations on the
other Microsoft Dynamics CRM 4.0 system. In this scenario, you cannot import the customizations.
This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

(http://support.microsoft.com/kb/949256/
)

Microsoft Dynamics CRM 4.0 updates and hotfixes

Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.

For more information about the terminology that is used to describe
Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

887283

(http://support.microsoft.com/kb/887283/
)

Microsoft
Business Solutions CRM software hotfix and update package naming standards

Article ID: 948043 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kbfix kbautohotfix kbexpertiseinter kbmbscustomization kbmbsmigrate kbqfe kbhotfixserver KB948043

Read the original post:
You cannot import the customizations from a Microsoft Dynamics CRM 4.0 system that you upgraded to another Microsoft Dynamics CRM 4.0 system that you also upgraded

Error message when you try to resolve a case in Microsoft Dynamics CRM: "There are not enough contract item allotments to resolve this case"

When you try to resolve a case in Microsoft Dynamics CRM, the case remains active. Additionally, you cannot click OK to resolve the case when you receive one of the following error messages.

Microsoft Dynamics CRM 3.0

There are not enough contract item allotments to resolve this case. Do you still want to resolve the case?

Microsoft Dynamics CRM 4.0

There are not enough contract items allotments to resolve this case.”

Note In Microsoft Dynamics CRM 4.0, you do not have an option to continue.

Additionally, you receive the following error message in the Web browser window:

Server Error in ‘/’ Application.

Allotments: remaining + used !=total

Allotments: used > total

If the DevErrors logging process is enabled, the following error message is logged:

Error: Exception of type System.Web.HttpUnhandledException was thrown.

Error Number: 0x800404F2

Error Message: The allotments remaining is invalid

This behavior occurs because Microsoft Dynamics CRM does not allow for negative allotments on a contract line. For example, consider the following scenario:
  • You create a Time Allotment Type contract.
  • The contract has a contract line that has the total minutes specified. For example, the Total Minutes field contains a value of 45.
  • You create the case. Then, you select the contract.
  • You enter a time in the Billable Time field. This time is more than the time in the Total Minutes field on the contract line.

In this scenario, when you try to resolve the case, you experience the behavior that is mentioned in the “Symptoms” section.

To resolve this behavior, resolve the case by using the allotments that remain. For example, resolve the case by entering billable time that is equal to the number of allotments that remain in the Total Minutes field on the contract line. Then, if you must have additional billable time, you must create a new contract line and a new case.
This behavior is by design.

Article ID: 947998 – Last Review: January 17, 2015 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 4.0
  • Microsoft Dynamics CRM Online Professional Edition
  • Microsoft Dynamics CRM Online Professional Plus
kbnosurvey kbarchive kbfreshness2008 kbmbscrmonline kbmbsservice kberrmsg kbexpertisebeginner kbtshoot kbmbsmigrate kbprb KB947998

See the original article here:
Error message when you try to resolve a case in Microsoft Dynamics CRM: "There are not enough contract item allotments to resolve this case"

How to print the Vendor EFT Bank List report in Microsoft Dynamics GP 10.0

In Microsoft Dynamics GP 10.0, the Electronic Funds Transfer (EFT) for Payables Management program code was merged with the Microsoft Dynamics GP core dictionary. In versions earlier than Microsoft Dynamics GP 10.0, the EFT Maintenance Report printed the EFT vendors. The EFT Maintenance Report is no longer available in Microsoft Dynamics GP 10.0. This article describes how to print the Vendor EFT Bank List report in Microsoft Dynamics GP 10.0. The EFT Bank List report contains EFT vendor information.
To print the Vendor EFT Bank List report in Microsoft Dynamics GP 10.0, follow these steps:
  1. On the Reports menu, point to Purchasing, and then click Setup/Lists.
  2. In the Report list, click Vendor List, and then click New.
  3. In the Purchasing Setup Reports Option window, type a name in the Option field.
  4. Click to select the Include Bank Information check box to print only vendors that are set up for EFT.
  5. In the Sort list, click a sort.
  6. Enter a Range area, specify a range.
  7. Click Destination, specify a destination for the report, and then click OK.
  8. Click Save, and then close the Purchasing Setup Report Options window.
  9. In the Purchasing Setup Reports window, click the option name that you created in step 3, click Insert, and then click Print.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Article ID: 947516 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics GP 10.0
  • Electronic Funds Transfer for Payables Management
  • Payables Management
kbnosurvey kbarchive kbnomt kbexpertisebeginner kbmbsmigrate kbhowto kbexpertiseinter KB947516

Read more here:
How to print the Vendor EFT Bank List report in Microsoft Dynamics GP 10.0

No Financial Rows to Display – Epicor SQL

“No financial rows to display” This error occurs when generating reports for some accounts.
The report includes accounts that were set up incorrectly in Epicor. These accounts may have segments defined incorrectly in the general ledger and there is a mismatch between what was defined in the account code in glchart and in the segment field.
Verify that account segments are set up correctly and match the account number defined in Epicor.
To investigate if any of the segments were not set up correctly, you may need to run select statements on the company database through ISQL or Query Analyzer. The following example compares seg3_code information.
The query below will identify any mismatches between the account code field and the segment:

select account_code from glchartwhere right(account_code,10) <> seg3_code

Note: The script above assumes the third segment to be the last 10 digits of the account code. You are extracting the first 10 characters from the right and comparing them with the segment field. You can easily modify this to search any size or particular segment.

Article ID: 965982 – Last Review: January 17, 2015 – Revision: 2.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive KB965982

See original article:
No Financial Rows to Display – Epicor SQL

Report Server – Processing Time and Finished Time

Why is the time that the report was processed later than the time that it finished?
The time that the report is processed is pulled from the workstation clock and the time that the report is finished is pulled from the Report Server clock. If the workstation and server times are different, there may be inconsistencies between the Processing Time and Finished Time values.

Article ID: 966007 – Last Review: January 17, 2015 – Revision: 3.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive KB966007

View article:
Report Server – Processing Time and Finished Time

Microsoft FRx 6.7 Service Pack 9 Installation for Geac SmartStream

Download the attached files for the latest Microsoft FRx 6.7 Service Pack and Documentation. Please contact your Microsoft FRx support provider to request assistance applying the service pack.

Article ID: 965734 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive KB965734

Visit site:
Microsoft FRx 6.7 Service Pack 9 Installation for Geac SmartStream

Microsoft FRx 6.7 Service Pack Release Notes History – EFI Logic

Please download the attached file that contains the previous service pack release notes.

Article ID: 965893 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive KB965893

Read this article:
Microsoft FRx 6.7 Service Pack Release Notes History – EFI Logic

Microsoft FRx 6.7 Vista Compliance

Microsoft FRx 6.7 Product Suite (Designer, Launcher, Drill Down Viewer, Report Server, Report Manager, and Web Administrator) is certified to run on Microsoft Vista as of Service Pack R09670.

Version 6.7 is the only version certified to run on Vista, and Service Pack R09670 is required if the Operating System is Windows Vista.

Article ID: 965848 – Last Review: January 17, 2015 – Revision: 2.0


Applies to
  • Microsoft Business Solutions for Analytics–FRx 6.7 Desktop
  • FRx Financial Reporter 6.5
kbnosurvey kbarchive KB965848

Visit link:
Microsoft FRx 6.7 Vista Compliance

Hotfix rollup 951969 is available for the Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0

Hotfix rollup 951969 for the Spanish-Latin American (ESLA)
version of Microsoft Dynamics GP 10.0 is available. This hotfix rollup is
cumulative. This hotfix rollup includes all earlier service packs and hotfixes.
For example, Service Pack 2 is included in this hotfix rollup.

This
hotfix rollup corrects the following problems for the Spanish-Latin American
version of Microsoft Dynamics GP 10.0.

Collapse this tableExpand this table

Module Problem
Payroll When you create a General Ledger batch in
Payroll, the General Ledger batch is unbalanced. This problem occurs if a pay
run uses a garnishment deduction type.
Inventory When you use an in-transit transfer in the
Receivings Transaction Entry window, the decimal places for
a quantity are
missing.
Inventory When you post multiple in-transit
transactions in an in-transit inventory receipt, Microsoft Dynamics GP creates
duplicate records in the inventory instead of posting the transactions to the
Purchase Order Processing tables.
Inventory An inventory transfer transaction does not
write the
correct costs to the IV10200 table.
Inventory The QTYONHND field in the IV10200 table is
updated by an
incorrect amount when you perform a virtual override process and a backdated
transaction. Therefore, the average cost is incorrect.
Field Service Microsoft Dynamics GP 10.0 stops
responding when you try to print a Sales Order Processing (SOP) edit list for
an audit trail.
Project Accounting When you try to post a transaction
that is created from a project allocation, you receive the following error
message:
“A miscellaneous log has already been posted for this
miscellaneous ID/period.”
Project Accounting You cannot process a summary tax
level edit in a Return transaction or in a Credit transaction if Project
Accounting is installed.
Project Accounting The PA Check Links process incorrectly sets the PABilling_StatusN
field in the PA31102 table for invoice variance transactions.
Project Accounting When you apply a retainer fee to a
Multicurrency Management project billing, Microsoft Dynamics GP 10.0
creates an additional payment in Receivables Management and additional
distributions in General Ledger.
Project Accounting When you run the PA Check Links process on the PA Billing Transactions table, Microsoft
Dynamics GP 10.0 incorrectly resets the value in the Post to
RM
field to 0.
Project Accounting When you perform a revenue
recognition process, Microsoft Dynamics GP 10.0 uses the Billings in Excess of
Earnings (BIEE) distributions instead of using the Earnings in Excess of
Billings (EIEB) distributions.
Project Accounting Microsoft Dynamics GP 10.0 creates
an
incorrect profit amount when you process multicurrency
projects.
Project Accounting When you change a fee amount and
an exchange rate, the functional currency distribution amounts in a billing is
incorrect. For more information, click the following
article number to view the article in the Microsoft Knowledge Base:

941381

(http://support.microsoft.com/kb/941381/
)

The functional currency distribution amounts are incorrect in Project Accounting in Microsoft Dynamics GP 9.0

Project Accounting You cannot print a recipient-created tax invoice in the Receivings Transaction Entry window.
Purchase Order Processing You can unexpectedly change
the PURCH account for purchase order returns.
Purchase Order Processing You can no longer add an
account profile (red) to a PURCH account.
Sales Order Processing You cannot save a country code
in the Sales Ship To Address Entry window.
Sales Order Processing If the Override Quantity to Invoice with Quantity Fulfilled check box is selected in the Sales Order Setup window,
Microsoft Dynamics GP 10.0 deletes
the taxes unexpectedly.
Manufacturing You configure an average perpetual item
by using the sales configurator. However, the item displays different costs in
Manufacturing and in Sales Order Processing.
Manufacturing The Data Collection transactions are
unavailable in the Job Link Maintenance window. This problem occurs if some
related manufacturing orders are linked to a job.
Manufacturing A material requirements planning (MRP)
job cannot recognize the fulfillment orders as expected.

Note All hotfix rollups for Microsoft Dynamics GP 10.0 are cumulative.
Each hotfix rollup contains all the fixes that are included in previous hotfix
rollups for Microsoft Dynamics GP 10.0.

Hotfix information

A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Technical Support for Microsoft Dynamics and related products to obtain the hotfix. You can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Technical Support for Microsoft Dynamics and related products by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft Dynamics GP 10.0 installed to apply this hotfix.

Removal information

You
cannot remove this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix
rollup.

File information

The Spanish-Latin American
(ESLA) version of this hotfix rollup has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Collapse this tableExpand this table

File name File version File
size
Date Time Platform
Microsoftdynamicsgp-kb951969-v10-esla.msp Not
applicable
176,396,288 09-Sep-2008 07:08 Not
applicable

Installation information

To install this hotfix, follow these steps:

  1. Download the latest update for Microsoft Dynamics GP 10.0.
    To do this, visit one of the following Microsoft Web sites, depending on
    whether you are a partner or a customer.

    Partner

    Customer

  2. Install the hotfix rollup on the computer that has the
    Microsoft SQL Server databases for Microsoft Dynamics GP. To do this, follow
    these steps:

    1. Double-click the file that you downloaded in step 1 to
      install the hotfix rollup.
    2. Start Microsoft Dynamics Utilities.
    3. In the Welcome to Microsoft Dynamics GP Utilities
      window, click Next.
    4. In the Upgrade Microsoft Dynamics GP window, click
      Next.
    5. In the Update System Tables window, click
      Update.
    6. In the Upgrade Companies window, click to select the
      check box next to each company name, and then click Next.
    7. In the Confirmation window, click
      Finish.
    8. In the Additional Tasks window, click Launch
      Microsoft Dynamics GP
      .
    9. Log on to Microsoft Dynamics GP. When you are prompted
      to include new code, click Yes.
  3. Install the hotfix rollup on each computer that has a
    Microsoft Dynamics GP client installation.

Hotfix rollup replacement information

Hotfix rollup 951969 contains all the fixes that are included in
the previous hotfix rollups for Microsoft Dynamics GP 10.0.

For more information about the previous hotfix rollups, click the following article numbers to view the articles in the Microsoft Knowledge Base:

940549

(http://support.microsoft.com/kb/940549/
)

The Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0 Service Pack 1 is available

946603

(http://support.microsoft.com/kb/946603/
)

Hotfix rollup 946603 is available for the Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0

947358

(http://support.microsoft.com/kb/947358/
)

Hotfix rollup 947358 is now available for the Spanish-Latin American versions of Microsoft Dynamics GP 10.0

948883

(http://support.microsoft.com/kb/948883/
)

Hotfix rollup 948883 is available for the Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0

943894

(http://support.microsoft.com/kb/943894/
)

The Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0 Service Pack 2 is available

Article ID: 951969 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics GP 10.0
  • System Manager
kbnosurvey kbarchive kberrmsg kbexpertiseadvanced atdownload kbmbsmigrate kbexpertiseinter KB951969

More here:
Hotfix rollup 951969 is available for the Spanish-Latin American (ESLA) version of Microsoft Dynamics GP 10.0

A workflow rule does not continue even though the "Wait" conditions are met in Microsoft Dynamics CRM 4.0

You use the Wait steps to wait for certain conditions to be met in the workflow rule that you created in Microsoft Dynamics CRM 4.0. However, when you run the workflow rule and the conditions in the Wait steps are satisfied, the workflow rule does not continue.

This problem may occur if the following conditions are true:

  • The workflow rule that contains the Wait steps is configured to wait until another entity that is created within the workflow rule meets some condition. For example, the status of the entity must change to a certain value.
  • The entity that is created in the workflow rule is updated very close to the same time that it is created, and the update satisfies the wait condition.

If these conditions are true, the workflow rule will not continue as expected. Instead, the workflow rule will wait indefinitely if the conditions can never be met again, such as when an activity is completed.

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

(http://support.microsoft.com/kb/949256/
)

Microsoft Dynamics CRM 4.0 updates and hotfixes

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

887283

(http://support.microsoft.com/kb/887283/
)

Microsoft Business Solutions CRM software hotfix and update package naming standards

Article ID: 951919 – Last Review: January 17, 2015 – Revision: 4.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kbautohotfix kbfix kbmbsworkflow kbmbsmigrate kbqfe kbHotfixServer KB951919

Visit link:
A workflow rule does not continue even though the "Wait" conditions are met in Microsoft Dynamics CRM 4.0

Page 22 of 982« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories