POST
|
Hi Marla, I have already done that. I worked with someone at technical services for several weeks on this issue but since AppStudio was still in Beta information was hard to come by for the tech who assisted me. He logged a bug as BUG-000090612: Incorrect date saved to database when using Quick Report Template in AppStudio Hope this helps, Matt
... View more
11-25-2015
06:49 AM
|
0
|
0
|
254
|
BLOG
|
Could you elaborate on how we would go about creating a secured feature service?
... View more
09-22-2015
07:52 AM
|
0
|
0
|
157
|
POST
|
I have already posed this question once and have yet to hear back. And since it was not fixed in Beta 4 I thought I would ask again. If you do not manually put the date in for a quick report app it logs it as either December 31, 1969 or January 1, 1970. Until this is fixed this pretty much makes that data value useless, unless the user manually puts in the correct date. And few people are going to do that when today's date is what comes up in the app.
... View more
09-21-2015
02:02 PM
|
0
|
3
|
2839
|
POST
|
Exactly. I assume there has to be some way to change this within the coding. However, my knowledge of coding ranges from very little to none. So I was hoping someone could tell me what code to write and where to write it. Even though I know very little coding I have gone into the QT creator and looked at all the different pages of coding trying everything I can to make it work. No luck so far. I have been in contact with someone at ESRI tech support for a couple weeks now and he has yet to find the solution. Hopefully this is addressed in the next Beta.
... View more
08-27-2015
07:11 AM
|
0
|
0
|
237
|
POST
|
Thank you! I look forward to seeing those changes implemented
... View more
08-20-2015
07:38 AM
|
0
|
0
|
372
|
POST
|
I had a question/concern regarding the feature services you use for a Quick Report app. I understand the need for these services to be made public. That allows the public editing rights to add their features to them. However, if you were wanting to implement an app like this for your organization (as my organization is considering doing), then there needs to be more security in place. As it is set up you are supposed to give editors the ability to add, update, and delete features. That means that were a user able to find the location of this feature service online they could potentially delete or change every feature. They wouldn't even need an arcgis online account to do this. That is problematic. If you set it to were the editors can only add features then even as the host of the feature service you still aren't able to delete these features. It seems like as the host of the feature service you should have some kind of 'master' control over the feature service. That way users can have the ability to add features and publicly access the feature service, but they wouldn't be able to tamper with the data. I just wanted to know if there is any way to set this up or if there any plans to implement a structure like this. Thanks!
... View more
08-18-2015
09:20 AM
|
0
|
4
|
3088
|
POST
|
My question relates more to the feature service you use when you create a quick report app. If you have a date field set up for your feature service then the default date in the app is always the current date. That would be fine, however, when the user doesn't change the date it becomes December 31, 1969 in your feature service. I know this has to do with Unix Time and that when the user doesn't go into the calendar the default date becomes 0(or December 31, 1969). While I do have a problem with that, I understand that's how its currently set up. My biggest issue is that by making the default date already set to the current date then the majority of users will not go into the calendar to reselect that date. So how can I make the date field blank or some arbitrary date that will implore more users to actually go into the calendar and set the date manually?
... View more
08-13-2015
12:17 PM
|
0
|
2
|
2125
|
Online Status |
Offline
|
Date Last Visited |
09-21-2023
03:08 PM
|