# Leveraging SFC designer from a Module

**URL:** <https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862>\
**Category:** Module Development\
**Created:** [October 29, 2024, 2:52am UTC](https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862 "2024-10-29T02:52:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mario\_Alvarado](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@Mario\_Alvarado](https://forum.inductiveautomation.com/u/Mario_Alvarado)\
**Post date:** [October 29, 2024, 2:52am UTC](https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862/1 "2024-10-29T02:52:32Z")

</div>

Hi There  
Quick questions:  
Is there a way to call the SFC designer from my custom Module to create a specific chart?  
Or is there any way to create charts using the SFC API?  
Thanks!

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 29, 2024, 3:41pm UTC](https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862/2 "2024-10-29T15:41:43Z")

</div>

No. As a general rule, modules are not expected or intended to interact with project resources - the _only_ source of project changes in Ignition is expected to be the end user working out of the designer.

---

<div class="post-metadata">

**Author:** ![Mario\_Alvarado](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@Mario\_Alvarado](https://forum.inductiveautomation.com/u/Mario_Alvarado)\
**Post date:** [October 29, 2024, 5:58pm UTC](https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862/3 "2024-10-29T17:58:49Z")

</div>

Thanks Paul  
Does SFC designer offer the ability of versioning control ? Is there a way to check in/check out charts ?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 29, 2024, 6:10pm UTC](https://forum.inductiveautomation.com/t/leveraging-sfc-designer-from-a-module/97862/4 "2024-10-29T18:10:35Z")

</div>

SFCs are project resources like any other in Ignition, and are written out to disk as more-or-less human readable XML files.

Version control is possible, though not the most user friendly, for Ignition projects as of Ignition 8.0:

> [@Guide for Version Control with Ignition](https://forum.inductiveautomation.com/t/guide-for-version-control-with-ignition/84004):
>
> Hey all, I've been working on developing some guides on how to use version control with Ignition in a team-based environment. If you've never used git, or just don't understand the nuances of how to use it with Ignition, you may find these documents useful to get you started. These are by no means comprehensive and are not any gold standard, but merely some guideposts as you find what will work best for you. Note: This isn't designed to be a substitute for studying the intricacies of Git, GitH…

> **[Ignition 8 Deployment Best Practices | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/tutorials/ignition-8-deployment-best-practices#source-control-system)**
>
> Learn more about best practices for setting up development and testing workflows

> **[Ignition 8 Deployment Best Practices](https://inductiveautomation.com/resources/article/ignition-8-deployment-best-practices)**
>
> Inductive Automation provides this helpful guide for deploying Ignition applications. The guide offers Ignition 8 best practices for setting up development and testing workflow.