Terje Nilima Monsen

I second this. Having the drop down show 365 when the path is Office -> Word -> 365 is not really helpful, and duplicating "Word" is not much better.

… and now it appears to be fixed.

… and it should be "Bug in" not "But in" o.0

Also, I would like to create some variables to use in stead of nesting the find statements like this.

I think I have found a bug in FIND() when creating a standard calculated attribute in Explore.

Scenario:
I have two tickets where one has a tag "cat_laptop" and the other has a tag "cat_software_ms-office_2019". These tags are used to categorize tickets.
I now want to create a report that shows all primary categories (the text after the first _ and before the second _)

Troubleshooting code

I create a new standard calculated attribute with this code:

IF
STARTSWITH([sakstagger], "cat_")
THEN
[Sakstagger]+" "+
FIND([Sakstagger],"_",4)
+" "+FIND([Sakstagger],"_",FIND([Sakstagger],"_",4)+1)
+" "+FIND([Sakstagger],"_",FIND([Sakstagger],"_",FIND([Sakstagger],"_",4)+1)+1)
ENDIF

Expected result:

cat_laptop -1 -1 -1
cat_software_office_2019 12 19 -1

Actual result:

cat_laptop 3 3 3
cat_software_office_2019 12 19 19

To me it appears that the FIND() function is missing the check that if the returned value is equal to or lower than the start index then it should return -1. In stead it returns the latest instance of the character and ignores the start index.

Possible workaround

I guess I could make a check myself, but that would defeat the entire purpose of the start index.

(Also I hope this is the right place to file bug reports. I couldn't find a better category.)