> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-post-to-nav-bc.md).

# Q\&A (Post to NAV/BC)

This article describes how troubleshoot [Post to NAV/BC](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md).

If [Stamp Events](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md) fails when [posting](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md) try use the *Manual post (journal only)* in the [Stamp Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md) page.

Standard NAV/BC posting of Productions *can* fail with the dialog *The operation has been finished. Do you want to post output for the finished operation?*, which can be solved in two different ways:

* Post the line manual using the *Manual post (journal only)* in the [Stamp Event](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/stamp-events-6182629.md) page.
* Remove the dialog from code:
  * For BC18 and newer set `IsHandled := TRUE` with `[EventSubscriber(ObjectType::Table, Database::"Item Journal Line", 'OnBeforeConfirmOutputOnFinishedOperation', '', false, false)]`
  * For older FOB installations(NAV2013 to BC14)
  * *Remote*/*Comment* `CONFIRM` for this in the table `Item Ledger Journal`.

## See also

[Post to NAV/BC](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/post-to-nav-bc.md)

## Reference

\
\\


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-jobmanager-product-overview/troubleshooting-and-known-issues/q-and-a-post-to-nav-bc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
