Settings Module not enabling fields for Company

[msochinski]

I created a new module settings app where all the settings apply at the global level, and most apply at the Company level. None apply at the org unit level. When I try to create an org unit setting, I put a Company in the Org unit field, but the fields which apply at the company level do not get enabled. Is there some additional configuration I need to do for this?

Thanks,
Megan

[kerri.h]

Hi Megan, is the Organizational Settings = true? Above the list of fields, next to the Global Settings checkbox?

[msochinski]

Hi Kerri, yes I have the Global Settings and Org Unit Settings flags checked, but not the Person Settings.

[msochinski]

This is what my app looks like:

[kerri.h]

That looks right. You should not need Person checked for what you need. Then in application builder you have an app over that table using the Module Settings App Type. Make sure to have these 3 fields defined in the Header Row.

1. GlobalSetting data item—Add on the header row to create a Global Setting checkbox in the Module Settings application. This is how you configure the module settings to be on a global level.
2. OrganizationalUnitName_Name data item—Add on the header row to create the Organizational Unit fields in the Module Setting application. This is how you configure the module settings to be on an organization level, and select the organization.
3. OrganizationalUnitName_OrganizationalUnitType date item—Add on the header row if you want certain fields to only be configurable when the org unit is of type Company.

[msochinski]

Hi Kerri, I added the same org unit fields as on the sales settings app and I am still not seeing any fields get enabled:

[kerri.h]

It works in existing applications, but I created a new one and I’m seeing the same thing as you. When the Org Unit Type is setup with Any the field is enable but not with Company. I’ll enter in a bug, can you enter in a ticket on your end and we can them together so you can follow it.

[kerri.h]

@msochinski this should be fixed when 25.1.07 is released to production.