SPENCER TESTING CSS

TABLE OF CONTENTS

• Use Case
• Use Case

Because of the complexity of storing custom CRM information, some changes to the CRM structure are not advised after user data has been stored in the database. Even for changes that are generally acceptable, always check with any other department (finance, mobilization, etc.) that may be using the field you would like to change.

Changes that are generally acceptable, per your organization's approval

• Adding new entity groups, entities, or fields
• Changing a field label in Motion 2
• • Changing a field label in Motion 2 does not change the field name in CRM
• Moving a field from one Motion 2 form to another

Changes that are acceptable for experienced admins or with WMTEK assistance.

• Change the name of a field in CRM
• • This will impact notification or display variables
• Moving a CRM entity from one entity group to another
• • This will impact notification or display variables
• Deleting fields from entities
• • Deleting a field from CRM will permanently delete any user data that had been stored in that field
• Changing a field’s field type
• • A TinyMCE field can be changed to a textarea or text field
  • A text area fields can be changed to a TinyMCE field or text field
  • A text fields can be changed to a text area or TinyMCE field.

Use Case

Changes that are not recommended for any users, or would require WMTEK development work

• Moving a question from one CRM entity to another
• • It is currently not possible in Site Stacker admin to move a field from one CRM entity to another. Two alternatives are currently possible:
  • • Make a new question in the new entity, and then search for and manually update all of the CRM profiles so that the data is listed on the new field instead of the old
    • Work with WMTEK to schedule a developer to manually move all the data from the old field to the new.

Use Case

In either case, after making this change, an admin would also need to update any Motion 2 forms that featured the old question and instead displayed the new one.

{% comment %}

{% raw %}

Here is some text that I don't want displayed and

{% some_liquid_stuff_that_I_don't_want_parsed %}

{% endraw %}

{% endcomment %}

.discussions-menu {
    display: flex;
    margin-bottom: 24px;
    border-bottom: 1px solid #f1f1f1;
    justify-content: space-between;
    align-items: baseline
}

.discussions-menu a {
    display: inline-block;
    margin-bottom: 24px;
    margin-left: 16px
}

Didn't find what you're looking for?

Visit the Site Stacker Monthly Releases page to view more release notes.

Important Requirement Before Going Forward

In order to connect using Azure for SAML and office 365, the client needs a "Azure Active Directory Premium P1" license. This is due to the fact that we will need to create an Enterprise App for SiteStacker and will need to use this claim with all the namespaces removed.

Warning!

We've found that editing this part of the code usually requires a WMTEK Developer.

Please fill out this form to schedule a developer to begin working on this part of the site for you.

Didn't find what you're looking for?

Visit the Site Stacker Monthly Releases page to view more release notes.

Didn't find what you're looking for?

Visit the Site Stacker Monthly Releases page to view more release notes.

Didn't find what you're looking for?

Visit the Site Stacker Monthly Releases page to view more release notes.

Didn't find what you're looking for?

Visit the Site Stacker Monthly Releases page to view more release notes.

Updated on: 02/04/2026