04/18/2023 01:29 PM
Hi Team
After 3.17 Patch, the analytics history count is max 10 counts . Can we increase the value to more than that ?
We have other team's who just get analytics history access to check the history. Would they need any specific savrole access to see archived history ?
Thanks
Manisha Priyadarsini
04/18/2023 02:24 PM
Hi @manisha9084
Document says below:
Thanks
04/18/2023 03:01 PM
Yes you can increase the number and for archival only admin can see data. But you can try creating custom sav role as per your needs
04/19/2023 01:46 AM
04/19/2023 04:15 AM
Can you provide screenshot?
its configurable per report
06/20/2023 07:40 PM - edited 06/20/2023 10:53 PM
Hi Team,
We are also having same requirement and we are maintaining the analytics history more than 10 in SAVIYNT 5.5 SP3.6 (we can enter the number what we want in 3.6). However, the later versions introduced analytics history is drop-down count maxed 10. Currently we have patched 5.5 SP3.17 in our lower environment and would like to increase the value to more than 10.
If I understand correctly from the responses above, we can manage if we have special privileges. I can confirm that I have admin role, but dont't know where we can set in the config. So could you please provide if you have any documentation explaining the configurations and how we can manage the max number.
Screenshot of 3.17
Screenshot of 3.6
Regards
Yakub
08/02/2023 09:19 AM
I am on v5.5SP5 and we dont see drop down in the Number of Request to keep, we can give based on our requirement. Maybe something changed in the 3.17 patch, please check with Saviynt team.
08/02/2023 05:23 AM
Any way from Admin Config where you can change the history ?
Thanks
Manisha
08/02/2023 08:37 PM
@manisha9084 10 is the maximum for all 23.1 and above, 3.17 and above. You can set 10 as the highest value and not more.
08/02/2023 08:45 PM
Run Update Query
select ANALYTICSNAME,NOOFHISTORYTOKEEP from analyticsconfiges
update analyticsconfiges set NOOFHISTORYTOKEEP ='20' where ANALYTICSNAME='ABC' limit 1;
08/02/2023 08:48 PM
Thanks @rushikeshvartak but this is not advisable. There is a reason why the number of history to keep has been limited to 10 keeping performance impact in mind as a guardrail. Also it is not suggested to run these update queries using custom query jobs as it can corrupt the elastic data.
08/02/2023 08:51 PM
What happens customer migrating from v5.5 to v23.x having more than 10history ?
All data will be corrupted ?
08/02/2023 10:23 PM
No. During migration if the value is greater than 10, it will be set to 10.