# Child application deployment from parent application

**URL:** <https://forum.algorand.co/t/child-application-deployment-from-parent-application/8132>\
**Category:** General\
**Created:** [October 29, 2022, 4:21pm UTC](https://forum.algorand.co/t/child-application-deployment-from-parent-application/8132 "2022-10-29T16:21:25Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![elia](https://avatars.discourse-cdn.com/v4/letter/e/278dde/32.png) [@elia](https://forum.algorand.co/u/elia)\
**Post date:** [November 4, 2022, 5:17pm UTC](https://forum.algorand.co/t/child-application-deployment-from-parent-application/8132/8 "2022-11-04T17:17:37Z")

</div>

> [@Ben](#):
>
> In the latest beaker you can get most of those fields from the Precompile object itself:

That’s great!

In this case, for the previous example, I would have to create a comprehensive dictionary composed of the one returned by `get_create_config()` and the additional information for the other `TxnField`s I want to specify. Then the comprehensive dictionary could be passed to `InnerTxnBuilder.Execute(comprehensive_dict)`.

Is my understanding correct?

---

_[View the full topic](https://forum.algorand.co/t/child-application-deployment-from-parent-application/8132)._