Latest Contributions by SeanGambrel

‎02-04-2015

Hi Ryan, Thank you so much for all the help so far. I don't want to consume any more of your time, but I'm not having an success. Would you mind looking at my definition below and see if anything basic really jumps out at you? PARCELSJOIN = name of the view I'm creating gisdata.GISADMIN.PARCELS = geometry gisdata.GISADMIN.PARCELDATA = table TEST = temporary value, as you mentioned above. CREATE VIEW PARCELSJOIN AS SELECT TEST.ACCOUNT, TEST.MAP_LOT, TEST.OWNER1, TEST.OWNER2, TEST.OWNER_ADD1, TEST.OWNER_ADD2, TEST.OWNER_ADD3, TEST.OWNER_ADD4, TEST.OWNER_ADD5, Spatial.* FROM gisdata.GISADMIN.PARCELS AS Spatial INNER JOIN gisdata.GISADMIN.PARCELDATA AS TEST ON Spatial.TAX_ACCT = TEST.ACCOUNT Any thoughts?

‎02-03-2015

Hi Ryan, Well, this is getting a little advanced for me, but I'm not afraid to tinker. So in the definition above, I'm confused about the "TEST" prefix on all of the fields. Do I leave that as-is, or is it a temporary value, or am I supposed to replace that with a value from my own database? And, "FIELDNAME1" is the join field (for both the table and geometry), and "Fieldname2-8" are the fields from the table that I want joined to the geometry? So would my query look like this, for instance: CREATE VIEW JOINEDPARCELS AS SELECT TEST.ACCOUNT, TEST.MAP_LOT, TEST.PROP_ADDRS, TEST.OWNER, TEST.ACRES, spatial.* FROM PARCELPOLY AS Spatial INNER JOIN PARCELTABLE AS TEST ON Spatial.ACCOUNT = TEST.ACCOUNT Again, thank you for the help!

‎02-02-2015

Hi Ryan, I'd like to try this out! I've not created a database view before, perhaps you can give me a nudge in the right direction? I have a few questions: 1. You say this is created "for the mapservice" - but just to clarify, this is something that you create in SDE, not in a map document, correct? 2. What kind of view did you build? Was it a true database view or a spatial view or a versioned view? 3. If the geometric data is going to be continually edited (but the table is static), will this impact which kind of view I need to create? Will the geometric data still be editable (via version)? Thank you Ryan (and everyone else who's chimed in)! Sean

‎01-29-2015

Yup. Single line geocoder wouldn't build. Walked through it with support in a few different configurations. I suspect its the join again.

‎01-29-2015

Interestingly, Jacob, I attempted to build a geocoder that looked at Property Address (values from a field, not a geometric locator), but it couldn't be built with our data for some reason that's still a bit unclear to me. Again, I engaged Tech Support on this issue and the reason they gave is that the data didn't have enough parameters or something to that effect. I'm still waiting to hear back if they have another solution. I'm really striking out here.

‎01-29-2015

Hi Lon & Jacob, I've been in touch (for weeks) with Tech Support and they now tell me this is a server-side bug. I believe the issue is that the data I need to query is an SDE Feature Class joined to an SDE table, and that is creating an error somewhere. For what its worth, the query widget appears to locate the value in the table (it says that there is one feature identified), but then immediately throws a generic "Query Error!" message, I believe when attempting to highlight and zoom to the feature. Tech Support has a temporary workaround involving exporting the data to a separate file GDB. This is fine in the very short term, but is not a good long-term solution (kinda negates having a server if you're just posting a copy every so often, right?). So this is all to say that if the geocoding (or other) widget offers a more immediate and permanent solution, I would consider it.

‎01-29-2015

Hi Ben, Unfortunately, I am limited to the OOTB tools included in the App Builder for Portal. I don't have the skills or support to build / modify an app myself. (as ever, I am a geographer, not a programmer!). It would be nice if the OOTB tools were a little more fully-featured or configurable. Thanks for the input! Sean

‎01-28-2015

Wow, no responses... Perhaps I'll ask a very slightly related question: Is there a way to use the Geocoding Widget without building an address locator? Its looking like that is the widget I will need to use, but my data is not set up correctly for use with a locator. Any thoughts?

‎01-26-2015

Is this the proper workflow, or is there a better tool / workflow that I am missing? How have others provided Search abilities in their web apps?

‎01-23-2015

Hi all, We are in the process of upgrading our server from 9.3 to 10.3, and I am attempting to re-create our flex apps using the App Builder. We are running a federated server and I am building apps via Portal. The first thing I noticed is with App Builder is that there is no "search by attributes" functionality, which is really the fundamental use in all of our flex apps. Typically users start by searching an address (located in an attribute field) or a facility ID #. Essentially users enter a value and the attribute table is searched and matching features are highlighted... Regardless, this functionality does not appear to be there "out-of-the-box", though one can configure the Query widget or use the Geocoding widget to approximate it. I started with the Query widget, thinking it would be the easiest to set up and maintain, however there is some bug or problem with the data that I and Tech support cannot figure out. So I'm now looking at using the Geocoding widget to perform the search task. In researching this, I am a little confused and hoped some of you could verify my understanding of the situation. As I understand it: 1. in order to use the geocoding widget, I will need to build a locator for each field and feature class I want to search. These different locators will be able to be selected via drop-down in the entry box of the geocoding widget. So for instance, if I want users to be able to search by Property ID, Owner Name, and Place name, I will need to build three locators for this one widget. Is this correct? 2. I've only built an address locator once and it was a long time ago. In reading through the resources, it seems like any locator that is built is considered an "address locator", even though it may use an attribute field instead of geometry to identify a feature. Is this correct or do I need to be looking at something else? For instance I may need to have manholes "searchable" by manhole ID number, which actually has little to do with geography. And "address locator" doesn't sound like the correct tool for this purpose. 3. As values in the attribute table (or a joined table) change, does the locator need updated manually, or will it always read the data dynamically? Thanks for the input. This is a bewildering workflow for what should really be out of the box functionality... Sean

‎08-18-2014

Hmmm. That sounds like something I'm really not equipped to remedy. My abilities with server are fairly limited. Unless you have other suggestions, I'll give tech support another try - though they're pretty hesitant to assist with 9.x. Thank you for your help. Worst case, this just has to function like this until we complete our server upgrade in the relatively near future. Again, Thank you Robert.

‎08-18-2014

Sorry, where do you mean exactly? I have been fiddling around with the widget's XML back and forth a bit throughout the day, trying (most likely re-trying) different combinations of variables. So perhaps you're just catching it then? Or maybe I'm missing something? It should be set back to false now.

‎08-18-2014

Yes, Cleared both the REST API cache and my browser's cache. Problem persists. Weird. When I search using the map-lot number field it only returns one matching result.

‎08-18-2014

I tried that but it still returned 500 results.

‎08-18-2014

Interesting. It doesn't appear that I can change that variable in the widget configuration (I do have it set to only display certain fields, but I think that's more of a display setting, post-query). The odd thing is that this used to work fine with a nearly identical table.

Online Status	Offline
Date Last Visited	‎03-30-2022 04:35 PM

My Ideas

Latest Contributions by SeanGambrel

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

Re: "search" feature in App Builder

"search" feature in App Builder

Re: Search App - Flex Viewer 2.5

Re: Search App - Flex Viewer 2.5

Re: Search App - Flex Viewer 2.5

Re: Search App - Flex Viewer 2.5

Re: Search App - Flex Viewer 2.5

Re: Search App - Flex Viewer 2.5

Select Largest Polygon in each parcel

"search" feature in App Builder

Cut & Paste Geometry AND ATTRIBUTES!

Cut & Paste Geometry AND ATTRIBUTES!