Dynamics AX 2012

  1. Position at which the bill of exchange is printed. Calculated from the top of the form to the position where the note starts. ...
  2. Position at which the promissory note is printed. Calculated from the top of the form to the position at which the note starts. ...
  3. Position records must have the position type of Job in order to be upgraded. Position records with a position type of Role ...
  4. Possible reasons for the log on failure include: (1) The current user is not a valid Windows user. (2) The user is not configured ...
  5. Posting definition '%1' is not set up for use with this module. Select a different posting definition, change the module ...
  6. Posting definition '%1' is not set up to create any ledger entries. The budget register entry was processed without ledger ...
  7. Posting definitions are defined with effective dates, and the specified posting definition is not active for this transaction ...
  8. Posting failed because there is a sales tax amount for a tax code that is not derived from the tax groups on the invoice. ...
  9. Posting failed because there is no sales tax amount on the electronic invoice, and the sales tax code is derived from the ...
  10. Posting is not possible because the last quality order generated in relation to this order failed to meet the minimum requirements. ...
  11. Prepare the header of the release order in the upper section of this form. If the agreement has quantity commitments, you ...
  12. Press 'Yes' to drop the table now, or press 'No' to leave the table and visit the SQL Administrator's menu at a later time. ...
  13. Price for cost category %1 was effective as per %2. Current system date is of %3. Record has been updated as effective from ...
  14. Price for item %1 was effective as per %2. Current system date is of %3. Record has been updated as effective from system ...
  15. Price on cost category %1 for site %2 effective from %3 has not been transferred, as an active price effective %4 already ...
  16. Prices may exist for the selected items. If you continue, both prices and items will be deleted. Do you want to continue? ...
  17. Problems resuming after critical shutdown. This could be due to network problems, or unavailability of the SQL database. ...
  18. ProcCategoryBuyingOrgPolicy table stores the legal entities a category policy applies to for various category associations ...
  19. ProcCategoryReceivingPolicy table stores the operating units a category policy applies to for various category associations ...
  20. Processed budget register entries can be reversed for budget type '%1.' If you continue, existing draft entries will not ...
  21. Product configurations (already created product variants) that can be reused when creating configurations using a sales configurator. ...
  22. Production order %1 has a warehouse at a site that is different from the site of the warehouses specified in the production ...
  23. Production order %1 has a warehouse in a site that is different from the site of the warehouses specified in the inventory ...
  24. Production order %1 has a warehouse in a site that is different from the site of the work centers specified in the production ...
  25. Production order %1 has corresponding physically updated inventory transactions on date %2 and cannot be ended before that. ...
  26. Production order '%1' consuming item '%2' has status '%3'. The standard cost conversion cannot be executed while not ended ...
  27. Production order '%1' for item '%2' has status '%3'. The standard cost conversion cannot be executed while not ended productions ...
  28. Products that are contained in a deleted catalog will no longer be available for order. Do you want to delete the vendor ...
  29. Project %1 cannot be updated. A project with the same name has already been integrated to Microsoft Project Server. Project ...
  30. Project %1 cannot be used for the alternate budget because it is a different project type. Select a project with the same ...
  31. Project %1 cannot be used for the alternate budget because it is outside the project hierarchy. Either change the project ...
  32. Project %1 is not associated with this project contract. Select a different project ID or clear the project ID to continue. ...
  33. Project '%1' includes transactions in category '%2', which is not available for this project. Add category '%2' to project ...
  34. Project stage rules do not allow the creation of an invoice proposal for project %1, with a %2 project type and a %3 project ...
  35. Provide a name to define a company web address (URL) for your Sites Services pages. For example, if you provide the name ...
  36. Provide the name of a SQL Server. To specify an instance, use the format MyServer\MyInstance. To specify the SQL Server instance ...
  37. Provides structure order within a dimension combination, the levels within each structure and the criteria order for a constraint ...
  38. Purchase agreement reference becomes invalid with this change, please select different project or remove agreement reference. ...
  39. Purchase order %1 cannot be confirmed, either because the transaction date '%2' is not part of an open fiscal period, or ...
  40. Purchase order %1 cannot be finalized on %2. The accounting date must be on or after the last accounting date %3 that is ...
  41. Purchase order %1 cannot be updated or posted because the limit for the prepayment is greater than the amount of the purchase ...
  42. Purchase order %1 has a prepayment amount that has not been applied to any invoice. The prepayment amount can be applied ...
  43. Purchase order %1 has an advance amount that has not been applied to any vendor invoice. The advance amount can be applied ...
  44. Purchase order %1 includes a carry-forward account that is not enabled for budget control. Either enable the account for ...
  45. Purchase orders were not created because the transaction date is not valid. Enter a date from a different fiscal period. ...
  46. Purchase requisition %1, Line %2, cannot be placed on a purchase order because its consolidation status is Pending consolidation'. ...
  47. Purchase requisition line number %1 cannot be canceled. Verify that it is in a status of 'Approved' and has no accounting ...
  48. Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase ...
  49. Qualified field names are required to use an ORDER BY and GROUP BY clause in the same SELECT statement. When using qualified ...
  50. Quantity %1 cannot be updated with inventory reference %2 because inventory transactions with status %3, %4 or %5 are insufficient. ...
  51. Quantity %1 cannot be updated with inventory reference %2 because inventory transactions with status %3, %4, %5 or %6 are ...
  52. Quantity to be used when allocating the specified charges on price per unit. Requires selection of the Incl. in unit price ...
  53. Query %1 cannot be made searchable because it does not have the SearchLinkRefName property or the FormRef property set on ...
  54. Query %1 cannot be made searchable because it does not have the TitleField1 field or the TitleField2 field set on the root ...
  55. Query %1 cannot be made searchable because it has a root table that is a transaction table with no index on the ModifiedDateTime ...
  56. Query %1 is searchable but it does not have the FormRef property set to a form on the root table %2. The search results will ...
  57. Query %1 is searchable but it does not have the SearchLinkRefName property set to a URL menu item on the root table %2. The ...
  58. Query fetch mode of 1:N is not supported by OData query services and queries that bind data sources to Views are not supported ...
  59. Query has an extra table '%1' with cardinality that could cause a cross-product. Cardinality of extra tables must only be ...
  60. Query {0} has a root table that is a transaction table, but has no index on the modifieddatetime field. This query will not ...
  61. Ready for operation. System Info: OS: %10 PID: %7 Executable: %2 Kernel build: %3 Configuration: %4 System directory: %5 ...
  62. Receipt advice %1 with inventory transaction identifier of %2 could not be matched with a purchase line. Kanban jobs could ...
  63. Receipt cannot be performed as receipt transactions cannot be identified completely. Receive update the transfer order with ...
  64. Recorded transactions exist in ledger '%1', in organization '%2', for the selected fiscal period. The Period %3 cannot be ...
  65. Recorded transactions exist in ledger '%1', in organization '%2', for the selected fiscal period. The Period %3 cannot be ...
  66. Recorded transactions exist in ledger '%1', in organization '%2', for the selected fiscal year. The fiscal year cannot be ...
  67. records in table '%2' retrieved from the database, but never used. Consider using FIRSTONLY, or a more selective WHERE clause. ...
  68. Recurring invoice %1 has been posted. Recurring invoice %2 was created and contains the selected invoices that could not ...
  69. RecVersion is needed for update but was not retrieved during read. This may be caused by group by or aggregate fields in ...
  70. Refill is needed on the picking location but a full pallet refill will lead to exceeding the maximum storage capacity. Consider ...
  71. RefRecId patching data has not been fully collected on the source system. Please wait until the Collect RefRecId Patch Delta ...
  72. Refunds found in the payment return file. Select 'Import refunds' and import the return file again to import the refunds. ...
  73. Register hours on the entry line, and press Enter . Click Transfer to transfer the hours to a journal in Project. Hour registrations ...
  74. RegisterOverrideMethod was called twice for the same object for method '%1'. You can only override a method once per instance. ...
  75. Registration of fee transactions is not allowed on projects of type %1. Fee transactions can be registered only on projects ...