# Reference forms in SDK by ID vs Name

**URL:** <https://community.feathery.io/t/reference-forms-in-sdk-by-id-vs-name/180>\
**Category:** Feature Requests\
**Created:** [October 13, 2023, 9:59pm UTC](https://community.feathery.io/t/reference-forms-in-sdk-by-id-vs-name/180 "2023-10-13T21:59:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![trevinbc](https://avatars.discourse-cdn.com/v4/letter/t/858c86/32.png) [@trevinbc](https://community.feathery.io/u/trevinbc)\
**Post date:** [October 13, 2023, 9:59pm UTC](https://community.feathery.io/t/reference-forms-in-sdk-by-id-vs-name/180/1 "2023-10-13T21:59:08Z")

</div>

It would be better IMO for the SDK to take in Form ID vs Form Name. Form names are generally internal and thought to be flexible. If you make a change you then break any reference to the old name (but the form ID should be the same).,

---

<div class="post-metadata">

**Author:** ![trevinbc](https://avatars.discourse-cdn.com/v4/letter/t/858c86/32.png) [@trevinbc](https://community.feathery.io/u/trevinbc)\
**Post date:** [October 27, 2023, 2:54pm UTC](https://community.feathery.io/t/reference-forms-in-sdk-by-id-vs-name/180/2 "2023-10-27T14:54:14Z")

</div>

Is there any chance to get this done? Every customer would benefit that embeds a form via the SDK. Using the form name is so brittle.

Since we are embedding a form in our new user onboarding flow, it is critical the form isn’t accidentally renamed.

We’ve had to name it “New User Onboarding - DO NOT RENAME” for fear of someone accidentally renaming and breaking our onboarding.