Latest Contributions by CandiceBardsley1

@ZhifangWang has this been resolved or added to current versions (well Portal 10.9.1 version specifically) as I too need my reports to be displaying the date range selected from the filter.  ... View more

I'm trying to do the same thing but in portal 10.9.1 - I can't see the options you show in the link provided - is that not an option in this version? ... View more

I'm trying to do the same thing but in portal 10.9.1 - I can't see the options you show in the link provided - is that not an option in this version? @TonghuiMing  ... View more

@TonghuiMing Is there a plan to update the button widget in experience builder (for Portal 10.9.1 and above) to include the same options to link to things as the AGOL button does? In particular the Block and Page Top options. It is a massive limitation to us and we need to keep using Portal instead of AGOL from a licensing perspective.  ... View more

@Richard_Purkis I'm having the same issue as Ben so will try the upgrade as well. Are you confirming though that a choice filter should work fine in the web form?  ... View more

@MichaelBruening thanks for the responses. The issue I have is identical to the question you linked in the above post - and it appears that worked. I might follow up on that post to see what Richard has to say. Thanks~! ... View more

@IsmaelChivite @MichaelBruening  Hey there - after some help regarding choice filters. I've set a simple one up in my survey 123 connect xlxs and it is working perfectly in the preview and also in the survey123 phone app once I've published. Brilliant. The issue I have is that I want the survey to be used within an experience builder on a laptop - the only way to embed that survey is to grab the link from Survey123 manager (via our portal). Again, I can embed the survey fine but in this setting the choice filter no longer works. I pick the initial geothermal field I want and instead of the wells for that field getting filtered by the choice filter for the next selection, the entire field is just blank.  Is this a known bug or issue with choice filters? Thanks in advance! ... View more

Awesome, that is working like a dream. Thanks for the help! ... View more

Thanks Xander, the double == solved my problem. Regarding the second option of having the threshold stored at feature level, I didn't do this because in the case of this feature class, some of the thresholds are actually when the pi_value is lower than the threshold number, so your script wouldn't work in this instance. Your first option of using a dictionary has taken what I originally asked for to the next level and is perfect for what I am after. For some reason though when I enter the script like you've written it I get Execution Error:Field not Found... Is there something missing or do I need to have a threshold entered for every object ID for this to work? ... View more

Hi John   I’ve tried this: If ($feature.OBJECTID=9) && ($feature["PI_Value"] >1951) {return "warning"} else {return "ok"} But get a parse error: unexpected token && So I must still be doing something wrong. ... View more