Simply investigate why long file paths are needed and remediate said issue.
If the filenames are currently parsed from their displayName or name - it would be more wise to utilize their templateId as that does not change but the displayName/name might.
If the filename is utilized within the csv generation - simply add an additional field when collecting said analytic rules from an endpoint - e.g - friendlyName and then filter it out on additional steps.
Simply investigate why long file paths are needed and remediate said issue.
If the filenames are currently parsed from their
displayNameorname- it would be more wise to utilize theirtemplateIdas that does not change but thedisplayName/namemight.If the
filenameis utilized within the csv generation - simply add an additional field when collecting said analytic rules from an endpoint - e.g -friendlyNameand then filter it out on additional steps.