Dynamics 365

  1. The %1 account type is only valid if the payment method function is %2 or %3. Select a valid account type for the payment ...
  2. The %1 automated task does not work with vendor invoices that are in an approval journal. Post approval journals manually. ...
  3. The %1 billing code does not exist or is being used by another billing classification. Select a different billing code or ...
  4. The %1 cannot be greater than the %2. Select the Apply prepayment action, unselect and reselect the prepayment to apply to ...
  5. The %1 check box cannot be cleared because the corresponding fast tab or activity hierarchy on the %2 form contains information ...
  6. The %1 configuration technology can only be defined if the configuration dimension is the only active dimension on the product ...
  7. The %1 configuration technology cannot be defined unless the configuration dimension is active on the product dimension group. ...
  8. The %1 dimension cannot have financial inventory activated without financial inventory being activated for the %2 dimension. ...
  9. The %1 dimension cannot have physical inventory activated without physical inventory being activated for the %2 dimension. ...
  10. The %1 dimension must be active. Select the %2 and %3 check boxes, ensure that the %1 dimension is not selected for any pending ...
  11. The %1 dimension must have financial inventory activated because the financial inventory is activated for the %2 dimension. ...
  12. The %1 dimension must have physical inventory activated because the physical inventory is activated for the %2 dimension. ...
  13. The %1 entity cannot be synchronized because it is now based on another table. Try again later and if the problem persists ...
  14. The %1 entity is used for the synchronization of one or more Outlook item collections.\If you delete this entity, all collections ...
  15. The %1 extension was successfully installed. All active users must log out and log in again to see the navigation changes. ...
  16. The %1 extension was successfully uninstalled. All active users must log out and log in again to see the navigation changes. ...
  17. The %1 field can only be selected if the line is for purchase or sale, the account type is %2, and the %3 field is selected ...
  18. The %1 field cannot be changed on a direct delivery purchase line since it may invalidate payments on the corresponding sales ...
  19. The %1 field is empty on one or more service contract lines, and service orders cannot be created automatically. Do you want ...
  20. The %1 field is not set up properly in the Currency Exchange Rates window. For %2 or the currency set up in the %3 field, ...
  21. The %1 field is not the first field that is specified for the %2 table. You must change the data export setup to list the ...
  22. The %1 file is an older version. Version %2 or newer is required for full functionality. Please contact your Microsoft Dynamics ...
  23. The %1 for %2 %3 has changed from %4 to %5 since the Sales Order was created. Adjust the %6 on the Sales Order or the %1. ...
  24. The %1 helps you create a new production journal name. Each group of fields is located on a separate page in the wizard. ...
  25. The %1 is not associated for use in the current company. Saving the record will allow the use of this %1 in this company. ...
  26. The %1 item cannot be processed because the company/separate division doesn't have a corresponding license (License type: ...
  27. The %1 query cannot be selected because it does not have the AllowCrossCompany property set to yes. In the AOT, change the ...
  28. The %1 relation to the %2 table does not have an upgrade script assigned. You must assign an upgrade script or exclude it ...
  29. The %1 table cannot be open, because the %2 or %3 fields are empty.\Fill in these fields with the appropriate values and ...
  30. The %1 workflow cannot start because all ending steps in the %2 sub-workflow have a value in the Next Workflow Step ID field.\Make ...
  31. The %1 workflow is used as a sub-workflow in other workflows, which you must disable before you can edit the %1 workflow.\Do ...
  32. The %1' field is not based on the Human resources position actions workflow type. Enter a workflow that is based on the Human ...
  33. The %1, which this report uses as a data source, has not yet been deployed. Deploy and process the %1 and then run this report ...
  34. The %1.1 table cannot be locked or changed because it is already locked by the user with User ID %13. Wait until the user ...
  35. The %1.1 table contains a Boolean field that does not use a BIT SQL Server data type. A value other than 0 or 1 has been ...
  36. The %1.1 table contains a Date field that uses invalid data for the time component of the DATETIME value: Field: %2.1 Value: ...
  37. The %1.1 table contains a field that has a SQL Server data type that cannot be edited by the Microsoft Dynamics NAV Development ...
  38. The %1.1 table contains a field with a Code, Text, or WideText value that is too large for the SQL Server data type: Record: ...
  39. The %1.1 table contains a field with a SQL Server value that is outside the allowable Microsoft Dynamics NAV Development ...
  40. The %1.1 table contains a field with a Variant SQL data type that can only be converted to a Varchar SQL data type: Field: ...
  41. The %1.1 table contains a field with an AutoIncrement value that does not match the SQL Server IDENTITY status: Field: %2.1 ...
  42. The %1.1 table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the ...
  43. The %1.1 table contains a Time field that uses invalid data for the date component of the DATETIME value: Field: %2.1 Value: ...
  44. The %1.1 table contains a value in a Code field that cannot be used with the Microsoft Dynamics NAV Development Environment: ...
  45. The %1.1 table contains a value in an integer Code field that cannot be used with the Microsoft Dynamics NAV Development ...
  46. The %1.1 table contains an Integer, Option, or Boolean field that uses a DECIMAL or FLOAT SQL Server data type. An invalid ...
  47. The %1.1 table has inconsistent SumIndexField values: Key fields: %6 SumIndexField table: %22 Contact your system administrator. ...
  48. The %1.1 table has multiple ROWVERSION columns in the SQL Server view description. Views can only have one ROWVERSION column. ...
  49. The %1.1 table has no ROWVERSION column in the SQL Server view description. A ROWVERSION column is required when BLOB fields ...
  50. The %1.1 table is a SQL Server temporary table. The Microsoft Dynamics NAV Development Environment does not support SQL Server ...
  51. The %1.1 table name conflicts with an existing SQL Server object %1.157. You must choose another table name or set the LinkedObject ...
  52. The %1.1 table references the SQL Server object %1.157, which is a system table or a view. You cannot change the LinkedObject ...
  53. The %1.1 table references the SQL Server object %1.157. You cannot link to the object when SumIndexFields have been defined. ...
  54. The %102.154 server does not contain Microsoft Dynamics NAV Development Environment license information. This information ...
  55. The %102.154 server is not running a supported version of SQL Server. Before this server can be used by the Microsoft Dynamics ...
  56. The %102.155 database on the %102.154 server cannot be opened by this version of the Microsoft Dynamics NAV Development Environment. ...
  57. The %102.155 database on the %102.154 server cannot be opened by this version of the Microsoft Dynamics NAV Development Environment. ...
  58. The %102.155 database on the %102.154 server does not contain Microsoft Dynamics NAV Development Environment system objects ...
  59. The %102.155 database on the %102.154 server must be converted before you can use it with this version of the Microsoft Dynamics ...
  60. The %102.155 database on the %102.154 server must be converted before you can use it with this version of the Microsoft Dynamics ...
  61. The %102.155 database on the %102.154 server must be converted before you can use it with this version of the Microsoft Dynamics ...
  62. The %102.155 database on the %102.154 server must be converted before you can use it with this version of the Microsoft Dynamics ...
  63. The %102.155 database on the %102.154 server must be converted before you can use it with this version of the Microsoft Dynamics ...
  64. The %102.155 database on the %102.154 server must be converted by the Microsoft Dynamics NAV Development Environment before ...
  65. The %2 derogatory tax model has not been assigned to this asset group. You cannot assign depreciation convention %1 to the ...
  66. The %2 derogatory tax model has not been assigned to this asset group. You cannot assign depreciation convention %1 to the ...
  67. The %2.1 FlowField in the %1.1 table is not a Boolean field. If a FlowField CalcFormula starts with 'Exist(.', then the FlowField ...
  68. The %2.1 FlowField in the %1.1 table is not an Integer field. If a FlowField CalcFormula starts with 'Count(.', then the ...
  69. The '%1' backup was successfully restored. User information was unable to be retrieved (Windows Error Code '%2'). A Windows ...
  70. The '%1' column can only contain '%2' characters for the entity '%3'. Data longer than this limit will be truncated on import. ...
  71. The '%1' document type is already in use as an attachment and cannot be used. Select a document type that has not been used. ...
  72. The '%1' link cannot be removed because warehouse %2 is part of replenishment rules %3. Please update the replenishment rules ...
  73. The '%1' object/column name in the %102.155 database contains one of the following characters: %22 These characters cannot ...
  74. The 'revision' part of the provided ApplicationVersion {0} is lower than the 'revision' part of existing version {1} in the ...
  75. The 'transfer to' or 'transfer from' budget model that you entered during the transfer process does not exist. Select a different ...