Dynamics NAV 2015

  1. The WordMergeDataItem property is set to DataItem '%6'. Only data items with DataItemIndent=0 can be specified in WordMergeDataItem. ...
  2. The {0} cannot register itself with SQL Server "{1}" in database "{2}" at startup and will try again when the first client ...
  3. The {0} database on the {1} server cannot be opened by this version of Microsoft Dynamics NAV Server because the database ...
  4. The {0} database on the {1} server must be converted by {2} before you can use it with this version of Microsoft Dynamics ...
  5. The {0} FlowField in the {1} table is not a Boolean field. If a FlowField CalcFormula starts with 'Exist(.', then the FlowField ...
  6. The {0} FlowField in the {1} table is not an Integer field. If a FlowField CalcFormula starts with 'Count(.', then the FlowField ...
  7. The {0} record with the same EntryId has already been processed. It will not be possible to send post-update for the {1} ...
  8. There are changes related to the following primary key that can cause data loss in the new table. The changes cannot be handled ...
  9. There are entities which depend on this entity. If you delete it, the relation to its dependencies will be removed.\Do you ...
  10. There are errors in the text conversion because of an incorrect internal buffer length in relation to text no. %1-%2. Internal ...
  11. There are errors in the text conversion because of invalid .stx syntax. The error occurred in the file %11 on line %12 in ...
  12. There are errors in the text conversion because text no. %1-%2 is too long for the internal buffer. Internal error: 47-%0 ...
  13. There are errors in the text conversion because the correct level of file must be the first line of fin.stx. The error occurred ...
  14. There are errors in the text conversion because the line is too long. The error occurred in the file %11 on line %12 in the ...
  15. There are errors in the text conversion because the same text is defined more than once. The error occurred in the file %11 ...
  16. There are errors in the text conversion because the text is too long. The error occurred in the file %11 on line %12 in the ...
  17. There are errors in the text conversion. The error occurred in file %11 on line %12 in text '%13'. The syntax is invalid ...
  18. There are event triggers associated to the global variable %6. Deleting the variable will delete the event triggers and their ...
  19. There are event triggers associated with the control %6. Changing the ControlAddin will delete the event triggers and their ...
  20. There are general ledger entries, cost entries, or cost budget entries that are posted to the selected cost center. Are you ...
  21. There are general ledger entries, cost entries, or cost budget entries that are posted to the selected cost center. Are you ...
  22. There are general ledger entries, cost entries, or cost budget entries that are posted to the selected cost object. Are you ...
  23. There are general ledger entries, cost entries, or cost budget entries that are posted to the selected cost object. Are you ...
  24. There are more columns in the Clipboard than in the target grid. Not all columns will be pasted. Are you sure that you want ...
  25. There are more than %1 rows within the filters. Excel only allows up to %1 rows.\You can either narrow the filters or choose ...
  26. There are multiple tenants mounted on the server. Validating table layout changes to protect against data-loss is only supported ...
  27. There are no %1 instances available for this database. You must ensure that a %1 instance is running and is configured to ...
  28. There are no charts defined. \Read the following topic in Help for Microsoft Dynamics C5: "How to: Prepare Small-Business ...
  29. There are no tenants mounted on the server. Validating table layout changes to protect against data loss is only supported ...
  30. There are one or more Cash Flow Manual Revenues/Expenses with a Recurring Frequency.\But the Recurring Frequency cannot be ...
  31. There are one or more entries for which no payment suggestions have been made because the posting dates of the entries are ...
  32. There are problems with the %1 Approval Setup. Re-enter Approval Amounts and make sure that at least one user has unlimited ...
  33. There are several interfaces in the type library, which have the name you have specified. Click the assist-edit button to ...
  34. There are table relations defined for the table %1. If you indent the table, the relation will be deleted. Do you want to ...
  35. There are table relations defined for the table %1. If you unindent the table, the relation will be deleted. Do you want ...
  36. There are tenants specified in {0}, but an application database was not specified in the DatabaseName setting in the server ...
  37. There are too many dimensions. The variable is defined with fewer dimensions. For example: MyVar MyArray[MyVar MyArray[1,2 ...
  38. There are too many FlowFields in the window. A window can display a maximum of %1 FlowFields. Remove some of the fields from ...
  39. There is a checksum error in the fin.stx file. The file has been changed or corrupted since it was installed. Contact your ...
  40. There is a checksum error in the fin.stx file. The file has been changed or corrupted since it was installed. The error occurred ...
  41. There is a discrepancy between the posting date of the value entry and the associated G/L entry within the reporting period. ...
  42. There is a problem initializing the page preview. The preview window will not open, but you can continue designing and saving ...
  43. There is a problem showing the page preview. The preview window will close, but you can continue designing and saving the ...
  44. There is a syntax error in the import on line %3 in position %2 : %1. The AL code is not indented as much as the first line. ...
  45. There is a syntax error in the import on line %3 in position %2 : %1. The ControlAddIn component has to be installed to import ...
  46. There is an existing SQL Server instance named '%1' which is not 64 bit. The current '%1' SQL Server instance must be removed ...
  47. There is an invalid character in the Find expression '%12'. In Find expressions, you can use =, >, and < in combinations, ...
  48. There is an invalid character in the Find expression '{0}'. In Find expressions, you can use =, >, and < in combinations, ...
  49. There is insufficient memory to execute this function. This can be caused by recursive function calls that are used in the ...
  50. There is insufficient memory to execute this function. This can be caused by recursive function calls. Contact your system ...
  51. There is no system code page on the Microsoft Dynamics NAV Server computer that matches the %7 code page of the %22 collation ...
  52. There is no system code page on your computer that matches the %7 code page of the %22 collation for the %102.155 database. ...
  53. There is no system code page on your computer that matches the %7 code page of the %22 collation for the %102.155 database. ...
  54. There is not enough disk space to install the selected product components. Create more free space on the selected drive and ...
  55. There is not enough memory available on the computer running Microsoft Dynamics NAV Server to perform the current activity. ...
  56. There is not enough memory to execute this function. If you work in a single-user installation, you can try reducing the ...
  57. There is not enough space on the disk to contain the entire title of the object file. Please choose a medium that has more ...
  58. There is not sufficient available space in the C/AL stack memory to execute this task. There are too many simultaneous activities, ...
  59. There is not sufficient space available in the database to perform this task. You can obtain more space by: Expanding the ...
  60. There is redundancy in the Shop Calendar. Actual work shift %1 from : %2 to %3. Conflicting work shift %4 from : %5 to %6. ...
  61. There must be a 'TRUE/FALSE' expression in the IF, WHILE or REPEAT sentence. The current expression is a Boolean type array. ...
  62. There must be a record variable in the WITH sentence. For example: WITH . DO . ; WITH . DO BEGIN . ; . ; END ; WITH MyRec ...
  63. There must be a record variable in the WITH sentence. The current variable has another type. For example: WITH MyRec DO . ...
  64. There must be an entry in the %1 table for the combination of VAT business posting group %2 and VAT product posting group ...
  65. There must be an IF sentence with an ELSE sentence. For example: IF . THEN . ELSE . ; IF . THEN IF . ELSE . ELSE . ; IF . ...
  66. These closing entries will not be transferred to a general journal before the program posts them to the general ledger.\ ...
  67. This .fob file is an old version which does not work with the Microsoft Dynamics NAV Development Environment. Use the Microsoft ...
  68. This address,&Directions from my company,Directions to my &company,Directions from &another address,Directions to an&other ...
  69. This answer reflects the state of the contact on %1 when the Update Contact Class. batch job was run.\To make the answer ...
  70. This assembly order may have customized lines. Are you sure that you want to reset the lines according to the assembly BOM? ...
  71. This batch job deletes entries. Therefore, it is important that you make a backup of the database before you run the batch ...
  72. This batch job deletes entries. Therefore, it is important that you make a backup of the database before you run the batch ...
  73. This batch job deletes entries. Therefore, it is important that you make a backup of the database before you run the batch ...
  74. This batch job deletes entries.Therefore, it is important that you make a backup of the database before you run the batch ...
  75. This change may have caused bin codes on some production order component lines to be different from those on the production ...