> For the complete documentation index, see [llms.txt](https://help.besmart.software/p4v/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/p4v/publisher4vlt-description/6-export-publishing-documentation-through-vault-publisher-add-in/6.2-default-option-for-associations-loading/6.2.1-parent-child-loading-based-on-publishing-configuration-availability.md).

# 6.2.1 Parent/Child Loading Based on Publishing Configuration Availability

This chapter describes the behavior of automatic parent/child entity loading based on the availability of publishing configurations.

It is demonstrated using the default settings for FILES described in the chapter [6.2](/p4v/publisher4vlt-description/6-export-publishing-documentation-through-vault-publisher-add-in/6.2-default-option-for-associations-loading.md).

<figure><img src="/files/qcd2wQh8IzbjPHWqQYqI" alt="" width="563"><figcaption></figcaption></figure>

## Assembly Structure and Published Files

The sample assembly and related files are visible in the image below. The V00000281.iam file was used to demonstrate the workflow.

<figure><img src="/files/ENNpIa6cdcXIDaOKmeTC" alt="" width="258"><figcaption></figcaption></figure>

## Different Cases Based on the Presence of Publishing Modules

The PackAndGo behavior depends on the availability of publishing configurations (if the configuration is enabled/disabled).

### Case 1: No Publishing Module is Available/Enabled

<figure><img src="/files/xjbMEoqMlcfrfm2BNYu4" alt=""><figcaption></figcaption></figure>

The PackAndGo command executed on V00000281.iam will load no child/parent entities, because no active publishing configuration/module is available.

<figure><img src="/files/9lGREOp8A0bLe1TiaKBk" alt="" width="563"><figcaption></figcaption></figure>

### Case 2: Only the Inventor PDF Configuration is Available/Enabled

<figure><img src="/files/0koJJEpfcoMPxhCASU1u" alt="" width="299"><figcaption></figcaption></figure>

The PackAndGo command executed on V00000281.iam will automatically load only the parent V00000282.idw association valid for the Inventor PDF publishing configuration.

<figure><img src="/files/RwEtj1yDYvDluWujeYQ5" alt="" width="542"><figcaption></figcaption></figure>

### Case 3: Only the Inventor STEP Configuration is Available/Enabled

<figure><img src="/files/qGwdloxwcBn0BsUC65Co" alt="" width="236"><figcaption></figcaption></figure>

The PackAndGo command executed on V00000281.iam will automatically load only the parent and child entities valid for the Inventor STEP publishing configuration. No additional (unwanted) parent (the IDW file) is loaded.

<figure><img src="/files/7ORfLlkEbkqQ2cCHhn52" alt="" width="563"><figcaption></figcaption></figure>

### Case 4: Both Configurations (Inventor PDF and STEP) are Available/Enabled

<figure><img src="/files/uJHipc4l6oDZ3Ksn959B" alt="" width="291"><figcaption></figcaption></figure>

When both configurations are enabled, a complete set of parent/child entities valid for the available publishing configurations is loaded.

<figure><img src="/files/MJKSqlMW0uWWxh4eY84v" alt="" width="563"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/p4v/publisher4vlt-description/6-export-publishing-documentation-through-vault-publisher-add-in/6.2-default-option-for-associations-loading/6.2.1-parent-child-loading-based-on-publishing-configuration-availability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.