I have this code (not exactly I modified the exact group_id's and numbers) as a client side calculated field in a UX
iif(Is_Active = 2 and Test_Field = 23,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 23,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 203,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 304,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 415,'a24f011111112345678902bc07b79ad6',iif(Test_Field = 203,'5f4c5ba7920843065b2b67',iif(Test_Field = 304,'b9c5eaeb3b574037839aae5694303db7',iif(Test_Field = 789,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 0 and Test_Field = 23,'84e4d0592a1e9d133bc269',iif(Is_Active = 1 and Test_Field = 0,'8687071d1cf342ac89c3cd6b669a5aa0','1234'))))))))))
The code for the calculated field works fine after its published, except when I save it, or rather hit OK - Alpha5 will lock up as not responding for HOURS! then I can save the UX and publish it.
Everytime I added an iif condition the time alpha locks up gets extended. The first few had it locked up about an hour now with all of the iif conditions it takes about a day of sitting there then its fine and I can save the UX and publish. I think I read somewhere that alpha converts the calculation to javascript so thats what going on when it is "not responding" anyone else have any thoughts on this iif statement
basically these are group_ids that I set depending on the 2 conditions.
is there a more efficient method?
I just added the last iif statement and I am certain that alpha will still be "not responding" in the morning. maybe tomorrow afternoon it will be fine I dunno the last time I did it it took about 14 hours to wake up.
I just updated to the latest build - but it was the same in the previous build.
iif(Is_Active = 2 and Test_Field = 23,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 23,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 203,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 304,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 1 and Test_Field = 415,'a24f011111112345678902bc07b79ad6',iif(Test_Field = 203,'5f4c5ba7920843065b2b67',iif(Test_Field = 304,'b9c5eaeb3b574037839aae5694303db7',iif(Test_Field = 789,'a24f011111112345678902bc07b79ad6',iif(Is_Active = 0 and Test_Field = 23,'84e4d0592a1e9d133bc269',iif(Is_Active = 1 and Test_Field = 0,'8687071d1cf342ac89c3cd6b669a5aa0','1234'))))))))))
The code for the calculated field works fine after its published, except when I save it, or rather hit OK - Alpha5 will lock up as not responding for HOURS! then I can save the UX and publish it.
Everytime I added an iif condition the time alpha locks up gets extended. The first few had it locked up about an hour now with all of the iif conditions it takes about a day of sitting there then its fine and I can save the UX and publish. I think I read somewhere that alpha converts the calculation to javascript so thats what going on when it is "not responding" anyone else have any thoughts on this iif statement
basically these are group_ids that I set depending on the 2 conditions.
is there a more efficient method?
I just added the last iif statement and I am certain that alpha will still be "not responding" in the morning. maybe tomorrow afternoon it will be fine I dunno the last time I did it it took about 14 hours to wake up.
I just updated to the latest build - but it was the same in the previous build.
Comment