Hi, how are you doing?
Thanks for reading this thread. We did some testing on 2.5.23.1, and it ssems that if we change the Organization (node) in the Organization Hierarchies (e.g. change mapping code from CHG to TAO), the users who were mapped to CHG would also be mapped to TAO after renaming. Can anyone please confirm this behavior?
Also, how would this "renaming" organization change the dynamic audience as well as My Reports?? Could someone please elaborate this a little bit? Thanks!
Sorry I meant "the users who were mapped to CHG would now be mapped to TAO after renaming"...
Hi Wen
If you use a dynamic audience that has a rule based on the organisation ID and you change the organisation ID the rule will remain the same so won't pick up the person in the audience that was based on the old organisation ID.
If you don't want this to happen you can use a rule that is based on selecting the organisation name from the hierarchy - if the hierarchy item changes name the rule will also change to include the updated organisation.
In general the same would apply to reports - any filter based on a value wouldn't be included but if the value is from a drop down list it would be included. The Content tab is based on the current organisation of the user so will display records based on this with the updated values included.
regards
Hi Craig,
Thanks so much for your reply. This is very helpful!
The key here is the "renaming" of an existing Organization Name and Organization ID number at the same time.
So based on our use case, say we renamed 22 (QCA) (for name) to 2 (SCL), and Organization ID number also from 22 (QCA) to 2 (SCL). Based on our testing, all of the existing users who were mapped to 22 (QCA) will now be mapped to 2 (SCL) after the renaming (good, this is what we want). But how about new users who will be automatically uploaded through Totara Sync (user.csv) process? If some of those users has the orgidnumber mapped to 2 (SCL), would they be mapped correctly (we haven't done this testing yet)? What happen later when we "recycle" the "22" code for some other locations, such as 22 (AAA)? Would there be any potential side effects (especially for dynamic audiences and My Reports, etc.), that might mix the new 22 (AAA) with the old 22 (QCA), etc.??
We just want to have a complete full picture before we do this change. For us, the goal is to "retire" 22 (QCA) organization code completely in the system, without causing any side effects, etc., in the long run. Thanks again!
Hi Wen
If some of those users has the orgidnumber mapped to 2 (SCL), would they be mapped correctly?
The Audiences and reports that use the Orgidnumber would be mapped to the existing Orgid so would need to be changed to reflect the new orgid. Audiences and reports mapped to the hierarchy item (organisation name) would include the records with the new organisation name and number as it is still mapped rather than based on the value.
As long as you replace all the old organisation ID 22 with the new organisation ID 2 and modify the reports and audiences that have the organisation ID in it to organisation ID 2 then you can reuse the organisation ID of 22.
Hope this makes sense.
Craig
Hi Wen
If some of those users has the orgidnumber mapped to 2 (SCL), would they be mapped correctly?
The Audiences and reports that use the Orgidnumber would be mapped to the existing Orgid so would need to be changed to reflect the new orgid. Audiences and reports mapped to the hierarchy item (organisation name) would include the records with the new organisation name and number as it is still mapped rather than based on the value.
As long as you replace all the old organisation ID 22 with the new organisation ID 2 and modify the reports and audiences that have the organisation ID in it to organisation ID 2 then you can reuse the organisation ID of 22.
Hope this makes sense.
Craig
