Dynamics 365

  1. The minimum quantity cannot be less than the minimum inventory order quantity that is defined in the order settings of the ...
  2. The mobile client previewer is unavailable in this language. To use the Form Preview, activate the English language pack. ...
  3. The mobile device interface cannot be opened because either the display settings are not configured or they are configured ...
  4. The mobile workspace referred by AppId %1 is not found in database and no resource name has been specified in the workspace ...
  5. The model store contains one of the following label files: DMF, DMP, EPR, FBK, FPK, GLS, MCR, PDS, PRO, PSA, PSC, RET, REX, ...
  6. The model store contains one of the following label files: DMF, DMP, EPR, FBK, FPK, GLS, MCR, PDS, PRO, PSA, PSC, RET, REX, ...
  7. The model store has been successfully validated and is ready for use. The model schema version is %2. The model store is ...
  8. The model version catalog coverage is {0}. We recommend that you use a model version with catalog coverage of {1} or higher. ...
  9. The model version used must be successfully built before the model can be activated. Please wait for the model version build ...
  10. The MODIFY call is causing a duplicate key error. This typically happens when a concatenated secondary key and primary key ...
  11. The month that you selected is not in sequence, although it is required to be. Do you want to decrease every following month ...
  12. The most current version of Microsoft SQL Server Data-Tier Application Framework must be installed. Go to http://go.micr ...
  13. The most recent customized ribbon for a tab on this page cannot be generated. A previous working version of the ribbon is ...
  14. The most recent version of any hotfix model is installed on the VM. The following table lists hotfix models that were installed ...
  15. The movement type expresses the type of the process for the underlaying lines. E.g. production, sales, purchase. Predescribed ...
  16. The name '%4' contains one or more characters that cannot be used because it does not comply with the Common Language Specification. ...
  17. The name '%6' contains one or more characters that cannot be used because it does not comply with the Common Language Specification. ...
  18. The name '{0}' entered to sign off this deployment does not match the expected name '{1}'. Please enter '{1}' to sign off ...
  19. The name '{0}' entered to sign off this deployment does not match the expected name '{1}'. Please enter '{1}' to sign off ...
  20. The name '{0}' specified as the database name is not valid. Ensure that the name complies with SQL Server identifier rules. ...
  21. The name cannot start with an underscore (_) or with {0}_. It must start with alphanumeric characters, followed by an underscore ...
  22. The Name field on the BudgetPlanningProcess table is not using the expected BudgetPlanningProcessName EDT. Update the upgrade ...
  23. The Name field on the SysInetThemeTable is not using the expected WebThemeName EDT. Update the upgrade script to support ...
  24. The name of %1 %2 doesn't match the name of the element in the lower layer. Ensure that the element's name is the same as ...
  25. The name of an element cannot be duplicated within the content of a complex type (line: %1, pos: %2 and line: %3, pos: %4). ...
  26. The name of the company bank was changed. If you created prenotes with the old bank name, you must re-create new prenotes ...
  27. The name of the XSL file used to transform the compound xml from Finance and Operations format to External application format ...
  28. The namespace prefix '%16' has already been declared in another namespace. You must use a unique name for the namespace prefix. ...
  29. The namespace prefix '%16' has not been declared in a namespace. You must declare the namespace prefix in a namespace of ...
  30. The Namespaces property contains an empty Prefix field for a Namespace. An empty Prefix field sets the namespace as the default ...
  31. The NAS service cannot start on tenant '{0}' because the startup codeunit is not specified. You can specify the startup codeunit ...
  32. The net cash flow measurement is a calculated column and cannot be exported without amount columns that are based on transactions. ...
  33. The netting agreement does not have a customer and vendor defined. Select at least one customer and vendor from the available ...
  34. The network is not functioning correctly. A packet has been corrupted and returns a checksum error. This error indicates ...
  35. The network is not functioning correctly. A packet was sent to the wrong address. This error indicates that the network is ...
  36. The network path cannot be found. This message refers to the file %1 %2. The network server may be down, or the path may ...
  37. The new assignment end date you entered is before the start or end date of the current assignment. Enter a different end ...
  38. The new assignment position that you selected has a future assignment. The new assignment end date will be adjusted to be ...
  39. The new assignment start date you entered is before the start date of the current assignment. Enter a different start date ...
  40. The new benefit expiration date must be before the current benefit expiration date, equal to or after the benefit effective ...
  41. The new benefit expiration date must be equal to or before the current benefit expiration date, after the benefit effective ...
  42. The new configuration number %1 will exceed in %2 characters. Change the setup in the Generate items/dimensions form or change ...
  43. The new default value will not apply to items that use the current item category, '%1'. It will only apply to new items. ...
  44. The new devices do not meet the terms of the current license. The current license allows {0} full devices, {1} limited devices, ...
  45. The new dimension group cannot be assigned. Other financial dimensions apply and physical inventory transactions might exist ...
  46. The new dimension group cannot be assigned. Other financial dimensions apply and physical or financial on-hand inventory ...
  47. The new dimension group cannot be assigned. Other financial dimensions apply, while '%1' is set to Yes, and inventory transactions ...
  48. The new dimension group cannot be assigned. Physical inventory transactions might exist and/or financial inventory transactions ...
  49. The new dimension group cannot be assigned. The physical inventory has not reached zero on-hand, while '%1' is set to Yes. ...
  50. The new encryption key does not meet the strong encryption key requirements. The key must be between 10 and 100 characters ...
  51. The new expiration date must be greater than the old expiration date %1 and not greater than the end date of facility agreement ...
  52. The new fiscal year begins before an existing fiscal year, so the new year will be closed automatically.\Do you want to create ...
  53. The new grant was successfully copied from an existing grant. Add a grant number and save the grant. The Requested amount' ...
  54. The new item number %1 will exceed in %2 characters. Change the setup in the Generate items/dimensions form or change your ...
  55. The new method of a derived class is not guaranteed to call super() on the inherited class. Provide an unconditional call ...
  56. The new price for item/dimension %1/%2 is equal to the current active price and will not be activated. %3 = %4, %5 = %6, ...
  57. The new query is not compatible with the existing form data sources and the following artifacts and their subcomponents are ...
  58. The new transaction date that you entered on this purchase order is not valid. Enter a date from a different fiscal period. ...
  59. The new users do not meet the terms of the current license. The current license allows {0} full users and {1} limited users. ...
  60. The new {2} attribute is set as the primary name attribute for the {1} entity. The {1} entity already has the {0} attribute ...
  61. The next number for estimates has already been used. \ Please consult with your accountant, and then update the number sequence ...
  62. The next number for invoices has already been used. \ Please consult with your accountant, and then update the number sequence ...
  63. The No. field cannot be empty when the status of the Certificate of Supply is set to Required, Received, or Not Received. ...
  64. The node %1 in this hierarchy has already been selected for threshold validation. Only one node in a hierarchy branch can ...
  65. The node cannot be deleted because it contains one or more internal control documents or child nodes. Delete the documents ...
  66. The node factory for the operator with the symbol "{0}" did not create a {1} node. Please ensure that operator node factories ...
  67. The node for dimension %1 with criteria %2 for account structure %3 is marked optional. You must unmark the Optional checkbox ...
  68. The node for dimension %1 with criteria %2 to %3 for account structure %4 is marked optional. You must unmark the Optional ...
  69. The node for dimensions %1 with no criteria for account structure %2 is marked optional. You must unmark the Optional checkbox ...
  70. The node owner does not have any permission by default. To assign Read, Edit, Assign or Add/Copy permissions on the node ...
  71. The non-numeric item '{0}' with context '{1}' has a decimals or precision value. Only numeric items should specify decimals ...
  72. The non-numeric item '{0}' with context '{1}' has a unit reference. A unit reference must only be specified for numeric items. ...
  73. The Nota Fiscal eletrônica (NF-e) that has the access key %1 cannot be posted because the status of the NF-e is %2 at the ...
  74. The notification action that is specified by following parameters is not valid: codeunit ID = {0} and function name = {1}. ...
  75. The number in the 'Total units ready for invoicing' field cannot be changed when there are unposted invoice proposals associated ...