Shopify Connector
Microsoft BCApps issue #10243 (open); fix PR #10305 (open); Microsoft Learn: Synchronize and fulfill sales orders
The length of the string is 45, but it must be less than or equal to 35 characters.
A Shopify order (usually B2B or a draft order) has a purchase order number longer than 35 characters. Business Central cannot create the sales document. The Shopify order stays in error on the Shopify Orders page, and every retry fails with the same message. The number in the message (45 here) is the length of the PO number on that order.
Shopify Connector / Fulfillment
Microsoft BCApps issue #13812 (open, approved); Microsoft Learn: Troubleshooting shipment synchronizations
Fulfillment order line item does not exist.
You posted a sales shipment in Business Central, but 'Sync Shipments to Shopify' does not mark the Shopify order fulfilled. The Shopify Log Entry shows the userError 'Fulfillment order line item does not exist.' Shopify rejects the whole fulfillment, so even the correct lines on that shipment are not fulfilled. The posted shipment gets Shpfy Fulfillment Id = -1.
Shopify Connector / Inventory
Microsoft BCApps issue #8396 (closed for inactivity, not fixed); Microsoft Learn: Synchronize inventory with Shopify
The specified inventory item is not allowed to be adjusted via API. Example: if the inventory item is a parent bundle.
Stock levels stop updating in Shopify for many products at once, not just one. The inventory sync job can still look successful. In the Shopify Log Entries, the inventory request's response has a userErrors entry with this message, pointing at a bundle product's inventory item.
Shopify Connector / Webhooks
BCApps source: codeunit Shpfy Webhooks Mgt.; Microsoft Learn: Synchronize and fulfill sales orders; Shopify: Troubleshooting webhooks
A job queue entry in ready state already exists. Skipping notification.
You turned on 'Auto Sync Orders', but new Shopify orders arrive in Business Central late or not at all, and no error appears in Business Central. The text above is not shown to users. It is a telemetry message (event 0000K8K) the connector logs when it ignores a webhook. A related telemetry message is 'Webhook subscription is not found.' (0000K8H).
Shopify Connector / Customers & Posting Groups
Microsoft Learn: Troubleshoot the Shopify Connector (Known issues); Microsoft Learn: Synchronize customers and companies
Gen. Bus. Posting Group must have a value in Customer: 'YOUR SHOPIFY STORE'. It cannot be zero or empty
The connector stops with this error when it needs a customer built from your customer template. The name in quotes is your shop code, not a real customer. It can appear when the connector calculates prices (it uses a temporary customer built from the shop's customer template) or when it creates customers for new Shopify buyers.
Core BC / Dimensions
Microsoft Learn: Troubleshoot and correct dimensions (message template 'Select a %1 for the %2 %3 for %4 %5.'); Medius KB (same message from a BC integration)
Select a Dimension Value Code for the Dimension Code DEPARTMENT for G/L Account 8100.
Business Central refuses to post the order (or invoice) because one account or record on it requires a value for a dimension, and the document has no value for that dimension. Microsoft documents the message as 'Select a %1 for the %2 %3.' or 'Select a %1 for the %2 %3 for %4 %5.' In the UI the placeholders become the dimension code and the record that demands it, for example 'for G/L Account 8100' or 'for Customer 10000'. The order was imported fine; only posting is blocked.
Core BC / Item Tracking
TrueCommerce KB 11179926 (Dynamics 365 Business Central Error: You must assign a lot number for item xxx); Microsoft Learn: Track items with serial, lot, and package numbers
You must assign a lot number for item 1000.
Business Central will not post the shipment because the item is lot-tracked and the shipped quantity has no lot number assigned. The goods may already have left the 3PL warehouse, but the sales order stays unshipped in BC, so invoicing and inventory are behind.
Core BC / Currency
Ramp KB (BC sync error: There is no Currency Exchange Rate within the filter. Filters: Currency Code: {currency}); azurecurve (same error on sales invoice entry); Microsoft Learn: Synchronize and fulfill sales orders (shop currency must have exchange rates); BCApps issue #13518
There is no Currency Exchange Rate within the filter. Filters: Currency Code: EUR
Business Central cannot convert a foreign-currency document into local currency (LCY) because it finds no usable exchange rate for that currency. Creating the sales document (or posting it) stops. Integrations that push documents into BC report this as a sync error.
Shopify Connector / EDI / Master Data
TrueCommerce KB 11161773 (Internal_InvalidTableRelation ... Item Unit of Measure); dynamicsuser.net thread (same error with the Shopify connector); BCApps Shopify connector source
The field Unit of Measure Code of table Sales Line contains a value (BOX) that cannot be found in the related table (Item Unit of Measure).
Business Central cannot create the sales line because the unit of measure sent for the item is not one of that item's units of measure. The order does not become a sales document. In the TrueCommerce connector the message starts with 'Internal_InvalidTableRelation'.
Shopify Connector / Extensions
Microsoft Learn: Troubleshoot the Shopify Connector, Known issues; BCApps Shopify connector source (Shpfy Product Price Calc.)
The Sales Header does not exist. Identification fields and values: Document Type='Quote',No.='YOUR SHOPIFY STORE'
Adding items to Shopify or syncing products or prices stops with this error. No quote with your shop's code exists in Business Central, and none is supposed to: the connector builds a temporary quote in memory to calculate prices. Another extension tried to read it from the database and failed.
Shopify Connector / Sales Tax
BCApps source: Shopify Connector NA, codeunit Shpfy TMA Events (IncompleteBlockErr / RateConflictBlockErr); BCApps PRs #7453, #12561, #13209; Microsoft Learn: Set up and use Shopify Tax Matching; Taxes in imported Shopify orders
The Sales Document for Shopify order %1 cannot be created because Shopify Tax Matching could not resolve one or more tax lines to a Tax Jurisdiction. Open the order, choose Review Tax Match, assign a Tax Jurisdiction to every tax line, and approve the match on the review page.
US only. A Shopify order came in with tax lines such as 'NEW YORK STATE TAX at 4%'. Business Central needs a Tax Jurisdiction for each tax line and a Tax Area on the order. At least one tax line has no Tax Jurisdiction, so the connector holds the order and does not create the sales order or invoice. %1 in the message is the Shopify order number. A second variant reads: 'The Sales Document for Shopify order %1 cannot be created because a matched Shopify rate differs from the Tax Detail Rate.' That one means the jurisdiction was found, but the rate Shopify charged is not the rate in your BC Tax Details.
Warehouse & 3PL
BCApps source: BaseApp report Get Source Documents (Text010Err, NoNewShipmentLinesForSalesOrderErr, Text003Err); Microsoft Learn: Ship items
There are no new warehouse shipment lines to create. This usually happens when warehouse shipment lines have already been created for a sales order. Or there were no changes to sales order quantities since you last created the warehouse shipment lines.
Someone (or an automation) chose 'Create Warehouse Shipment' on a sales order, but Business Central created nothing. The order lines are already on an open warehouse shipment, or nothing changed on the order since the last shipment was created. The error offers an action to show the open warehouse shipment lines for the order. If no warehouse shipment lines exist at all, the older text 'There are no warehouse shipment lines created.' appears instead.
Job Queue & Core BC
Microsoft Learn: Database Lock Timeout Trace Telemetry (RT0012, RT0013); Monitoring SQL Database Locks (page 9511); Schedule jobs to run automatically
The operation could not complete because a record in the Sales Header table was locked by another user. Please retry the activity.
A background job (for example Shopify order import, background posting, or an EDI import) waited for a record that another session held locked. The wait timed out and the job stopped with status Error. The table name in the message tells you where the conflict is (Sales Header, a No. Series table, Item Ledger Entry, and so on). Newer versions can show different wording for the same situation, but the cause is the same.
Warehouse & 3PL
BCApps source: BaseApp table Sales Line (Text016, WhseRequirementMsg, CheckWarehouseForQtyToShip); codeunit Sales-Post (WarehouseRequiredErr); test SCM Warehouse VII; Microsoft Learn: Ship items
Warehouse Shipment is required for Line No. = 10000.
The sales line uses a location where 'Require Shipment' is turned on. Business Central wants you to ship through a Warehouse Shipment document, not from the sales order. You see one of three messages: (1) a warning when you set Qty. to Ship: 'Warehouse Shipment is required for this line. The entered information may be disregarded by warehouse activities.'; (2) an error 'Warehouse Shipment is required for Line No. = 10000.' when warehouse lines already exist for the line; (3) at posting: 'Warehouse handling is required for Document Type = Order, Document No. = ..., Line No. = 10000.'
Shopify Connector / API Limits
Shopify docs: GraphQL Admin API rate limits, GraphQL error codes, REST Admin rate limits; BCApps source: Shpfy Communication Mgt. (THROTTLED retry, HTTP 429 retry, telemetry 0000QWH); BCApps PRs #9146 and #10417
THROTTLED: The client has exceeded the rate limit. Similar to 429 Too Many Requests.
Shopify limits how much each app can ask per store. The connector uses the GraphQL Admin API, which charges each query a cost in points against a bucket that refills at a set rate by plan (Standard 100, Advanced 200, Plus 1000 points per second). When the bucket is empty, Shopify answers with a THROTTLED error (REST answers HTTP 429 with a Retry-After header). The connector retries automatically, so usually you do not see an error: syncs just get slow. You see an error only if the retries give up, as 'Error(s) on Shopify:' followed by Shopify's error text, on the Shopify Log Entries page.
EDI & Trading Partners
TrueCommerce Help Center article 16020861 (Dynamics 365 Business Central)
Application_DialogException Price and/or Discount is currently frozen on this sales line. Unfreeze before unit of measure code can be changed.
Transaction Manager exports an inbound purchase order (EDI 850) into Business Central. The export must change the Unit of Measure Code on a sales order line. Business Central refuses, because the price or discount on that line is locked. The sales order is not updated, and the 850 stays in error in Transaction Manager.
EDI & Trading Partners
TrueCommerce Help Center article 16053663; Equisys technote ZTN6028 (same error in Zetadocs Expenses)
Your license does not grant you the following permissions on CodeUnit 6989 Expense Attachment Mgt.: Execute.
After the environment updates to Business Central 28.3, Transaction Manager operations in Business Central fail with an Internal_ServerError. The message says the license does not allow CodeUnit 6989 Expense Attachment Mgt. EDI imports and exports stop until the cause is removed. Other apps that create purchase records see the same error.
EDI & Trading Partners
TrueCommerce Help Center articles 6433577, 6421581, 6475828, 6474238
Invalid ASN Type
You import an outbound Advance Ship Notice (EDI 856) from a Posted Sales Shipment into Transaction Manager, and the import fails with 'Invalid ASN Type'. A related symptom: the import works, but the Shipment Details tab has no Pack or Item data, so the ASN is empty. Either way, the retailer does not get a usable ASN.
EDI & Trading Partners
TrueCommerce Help Center article 6502495
There is nothing to post
A vendor sends an EDI 810 invoice. Transaction Manager exports it to Business Central to invoice the matching purchase order, and Business Central answers 'There is nothing to post'. No posted purchase invoice is created, and the vendor invoice stays unmatched.
EDI & Trading Partners
TrueCommerce Help Center article 6582275
The field Ship-to Code of table Sales Header contains a value (xxxx) that cannot be found in the related table (Ship-to Address).
A trading partner sends a purchase order (EDI 850) for a store or distribution center. Business Central cannot create the sales order, because the ship-to location code on the order does not exist for that customer. The PO stays in error in Transaction Manager. This is common when a retailer opens a new store or DC.
Warehouse & 3PL
Microsoft BCApps source: WhseValidateSourceLine.Codeunit.al (Text001) and SalesWarehouseMgt.Codeunit.al (SalesLineDelete); mibuso forum report
The Sales Line cannot be deleted when a related Warehouse Shipment Line exists.
A customer cancels a line or the whole order, or a Shopify/EDI update tries to remove a line. Business Central refuses, because the line is already on a warehouse shipment. The warehouse (your own or a 3PL fed from warehouse shipments) has the instruction to ship it. A related error appears if you change the line instead of deleting it: 'Quantity must not be changed when a Warehouse Shipment Line for this Sales Line exists'. The same check covers Type, No., Variant Code, Location Code, Unit of Measure Code, Drop Shipment, Qty. to Ship and Shipment Date.
Carrier & Shipping
FedEx Developer Portal (API Authorization docs; Best Practices) and Inlinex FedEx label error guide
401 Unauthorized — NOT.AUTHORIZED.ERROR: Access token has expired or is invalid.
Rate, label or tracking calls to FedEx fail for every shipment. Packing stations cannot print FedEx labels until a valid token is used.
Carrier & Shipping
Adobe ColdFusion community thread 'UPS REST API issue' (UPS response code 110609); Octolize UPS error 9120203
110609: All package dimensions are required and each must be greater than 0 for package 1.
UPS rejects the rate or label request for the package. No label prints for that shipment. A close variant is error 9120203: 'Missing or invalid Combination of package length, width, and height values for package'.
Job Queue & Core BC
Microsoft Learn: Task scheduler (AL methods that throw nonretriable exceptions in background sessions); microsoft/AL issue #5547; microsoft/ALAppExtensions issue #9801
Microsoft Dynamics 365 Business Central Server attempted to issue a client callback to show a confirmation dialog box: ... Client callbacks are not supported on Microsoft Dynamics 365 Business Central Server.
A job that works when a user runs it by hand fails when the job queue runs it. Typical cases: posting or releasing orders, an order import, or a report or export. The Job Queue Entry goes to Error and Show Error gives this text. Through an API or OData call the text says 'Business Central Data Services' instead of 'Server'.
Core BC / Purchasing
Microsoft BCApps source: SalesPost.Codeunit.al (DropShipmentErr); Microsoft Learn: Make drop shipments
You cannot ship sales order line 10000. The line is marked as a drop shipment and is not yet associated with a purchase order.
You post the sales order with Ship (or the integration posts it when the vendor reports shipment). Business Central stops, because the drop-shipment line has no linked purchase order line. Nothing posts.