Latest Contributions by AbiDhakal

Hey Dan, Thank you for the direction. I tried this expression, but it did not run for me. I probably did not know how to insert the right fields in the expression. Here is the expression:  var startDate = Date($feature.startDateField); var endDate = Date($feature.endDateField); var age = DateDiff(endDate, startDate, 'years'); return age; I only have created_date field and an Age field. I would like the derivation to populate the Age field by substracting current_date which I do not have from created_date. Thank you. Abi ... View more

Hello GIS friends, I am also having the same problem. Before the vacation I had tested across several Collector applications and they were all working fine, but now they are all saying Invalid URL. I worked with esri tech and they told me that it is a global problem and that esri is working to fix it. I have not seen any official notice from esri regarding the issue. Can anyone help, please? Thank you. Abi ... View more

Thank you very much Xander! ... View more

Hey Xander, Morning! What I am trying to do is create an attribute rule where by any point collected automatically also has its xy calculated in decimal degrees. Is that possible? Thank you. Abi ... View more

Sorry. I meant to say I have it in NAD_1983_UTM_Zone_16N and like you mentioned I want to obtain decimal degrees (WGS 1948). Would the same expression work with the OriginalShift and all? I'm actually trying to create an attribute rule for the xy fields to auto populate. Once again I'm sorry for the confusion. Abi ... View more

Hello GIS friends, This expression worked for me, but it is in meters. How can is change it to  WKID 3857 from within the expression? Thank you. Abi ... View more

Thank you so much Rachel. It really helped. Abi ... View more

Hey Brian, I'm late in the show, but I'm in the show now nonetheless. I'm having issue with date on the web appbuilder application versus the GIS Server date. The date field for the  feature service in the web appbuilder is not matching with the date field for the same feature layer for the same field on the Server. Pretty much what you are referring to in your message above. I do not have the advantage of create a new field and running the time zone conversion geoprocessing tool. My data is directly being fed to another system once I copy the layer from the Server. So, I can only copy the erroneous layer. A day in the data is making a lot of difference. Especially, for a new fiscal year date. I'm trying to put in 10/1/2018 for the start of a new fiscal year in the feature service in my web appbuilder, but the data on the Server is showing up as 9/30/2018, and for this reason any data that is being generated on 10/1/2018 is not being included in the current fiscal year. Has this problem been resolved? What is the workaround? Thank you for your help. Abi ... View more

Apparently, they have not fixed it! ... View more

Hey Kristy, Your manual date field should work. May be you have to try naming the field without the word date. I have not tried it myself. Should you try please let me know the behavior. Thank you. Abi ... View more

Kristy, I have not heard anything on the solution yet. I do not remember if I logged a bug back in the day for this case. Have you tried filtering with created_date and the download is failing. If so, then they have not worked on the resolution yet. What date field are you using? Thank you. Abi ... View more