The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Form Template Naming Restrictions
Hello,
Since when are Form templates no longer allowed to include a dot (.) or a hyphen (-)?
We built our naming convention using dots, and it is now unusable under these restrictions.
Please confirm when this change was introduced and what alternative naming format you recommend.
Best regards,
Can you also attempt to Rename the form and see if it also gives you the error? What version of OneStream are you currently using?
I tested this in the latest release (9.2) and see the same behavior, I am able to create a new form with the naming convention you have, but if I attempt to rename it with a similar naming convention it throws the error.
I would recommend opening a support case so the support team can look at this with you and possibly log this as a defect. If it will not allow you to do a rename or copy with this naming convention, it should also not allow this via a new form created from scratch.
Thank You
7 Replies
JJonesOneStream Employee
Is this happening only when you do a rename of an existing form? If you create a new Form and use the naming convention does it allow you to use 03.02 - OrderBook?
Hi there,
If I start my existing form from scratch I am able to create a new form using my old naming convention.
Just in case of a copy/paste from an exisiting one, it does not work.
We always use "_ underscore" in our names.
v9.0: try to rename newly created "- 1" to "- 2"- JJones
Can you also attempt to Rename the form and see if it also gives you the error? What version of OneStream are you currently using?
I tested this in the latest release (9.2) and see the same behavior, I am able to create a new form with the naming convention you have, but if I attempt to rename it with a similar naming convention it throws the error.
I would recommend opening a support case so the support team can look at this with you and possibly log this as a defect. If it will not allow you to do a rename or copy with this naming convention, it should also not allow this via a new form created from scratch.
Thank You
I am currently using the version 8.5.1.
By trying to rename it, it throws the error.I already opened a case and I guess the issue will be corrected in the next release of OS.
- JJones
Thank You for logging a case, it helps us track the customers who are facing these issues.
For an alternative naming convention, you could use an underscore (_) vs using a period or dash.
