Latest Contributions by TL2

‎09-28-2017

You can do this with SSMS or GeoEvent.

‎08-28-2017

I will work on getting you the karaf files. The connection does not drop after 24 hours. We have email alerts set up every 5 minutes. At one or more points within 5 minutes, not every 5 minutes, the connection will drop and we will get a few hundred errors like the one above.

‎08-28-2017

We keep receiving the error... --------------------------------------------------------------------------------------------------------------------------------------------------------------- Event #1: ID: 2017-08-27T17:58:58.060Zxxxxxxxxxxxx Source: GeoEvent Code: 2017-08-27T17:58:58.060Z Type: SEVERE Msg: Failed to start because layer information is not available ([PORTAL][FeatureService][FeatureService][0][FeatureServer])2017-08-27 11:59:03,210 --------------------------------------------------------------------------------------------------------------------------------------------------------------- The connection seems to fail for a very short period of time, our inputs check for new features every 60 seconds and will function properly once a connection successful. We are running 10.4.1 Portal/Server Federated with GeoEvent installed on a standalone machine. Anyway to keep the connection up without intermittent failures?

‎08-28-2017

How do we add this to our own App. Is it done in the web map?

‎08-04-2017

I did see that. When I change the instances though it seems to break it. The following scenario, with changes made in red, seem to break the HFS. But the ability to change them is available.

‎08-04-2017

Can you set pooling for a hosted feature service on a datastore for portal 10.4.1? Now, I know that you literally can go into service properties for that HFS and change the pooling but it seems to break the hosted feature service. Is this something that, while can be done, should not be done?

‎07-12-2017

I have attempted this but my input provides nothing to edit? Is portal different?

‎07-12-2017

I am trying to convert the attachment tables DATA tab (BLOB/VARBINARY) into Base64. USE UTILITIES SELECT CAST(CAST('' as XML).value('xs:base64Binary(sql:column("DATA"))', 'VARBINARY(MAX)') AS NVARCHAR(MAX)) FROM FeatureClass_ATTACH_evw WHERE REL_OBJECTID = '51' go Results: "�က䙊䙉Ā ĀĀ" Is there a way to convert the BLOB into Base64?

‎07-11-2017

Republishing a survey with Survey123 Connect after just updating some Coded Domain Values does update the options within the survey but does not update the domains in the HFS. How can I update the domains in the hosted feature service without loosing my data. When I access the Admin Rest endpoint it gives me the option to Update Definition but there is nothing to edit, the Input is blank. Portal Federated with Server 10.4.1

‎07-11-2017

I am seeing the latest update in AppStudio for Survey123 and Connect were on 6/18. Can the new 2.2 version be added soon please. Thanks.

‎06-23-2017

James Tedrick‌ I have been trying to set up a survey which is tied to a federated service with a repeat and attachments on both the FS and Table. I am receiving the error below when attempting to publish even though both of my services are set to Supports ApplyEdits With Global Ids: true. My FS - ID: 0 in service MXD. Global Ids enabled, attachments enabled (based on GIDS), editor tracking enabled, archiving enabled, indexed on globalid field (unique: yes, ascending: yes) Supports ApplyEdits With Global Ids: true at rest end point. My Table - ID: 1 in service MXD. Global Ids enabled, attachments enabled (based on GIDS), editor tracking enabled, archiving enabled, indexed on globalid field (unique: yes, ascending: yes) Supports ApplyEdits With Global Ids: true at rest end point. My FS and Table relationship: Simple, 1-M, No Notifications, Origin is FS, Dest. is Table based, primary key: GlobalID, foreign key: parentrowid I have created my survey and published it to the portal as a HFS. I then export as file geodatabase and import the feature layer and table into my sde and create attachments etc and relationships. Scenario 1 I publish an mxd with the IDs noted above. When I add the item description URL to my survey and delete the .itemINFO file I recieve the following error... I have verified that both my FS and Table both have Supports ApplyEdits With Global Ids: true. Scenario 2 When I create a new survey based on the Feature Service option within Survey123 and select the same feature service as above I receive the same error as above. In Scenario 2 it sets my attachments to false (probably because those image fields to not get carried through the feature layer. Should I be able to use a feature service with a related table federated with portal in a survey?? UPDATE: I changed my feature-table relationship to GlobalID and parentrowid (guid) and that fixed one error.

‎06-13-2017

I was able to use the submission url successfully. Archiving must be enabled. (add attribute index geoprocessing tool did not work, maybe I did that wrong) Also, the submission url formatting IS https://domain.com/arcgis//sharing/rest/content/items/xxxxxxxxxPortal Item IDxxxxxxxxxx IS NOT https://domain.com/arcgis/home/item.html?id=xxxxxxxxxPortal Item IDxxxxxxxxxx

‎06-09-2017

I would like more detail/documentation on publishing surveys with services federated with my portal and server. What are the requirements for the published feature service? I would like to take an existing survey, add the rest end point to the submission url and publish. Currently I am getting this error. My work flow: 1. Publish my survey to ArcGIS Portal 10.4.1. 2. Export my HFS as FG. 3. Create Service MXD with feature class from exported FG. (enabled attachments after adding globalids. Ran 'add attribute index geoprocessing tool') 4. Copy Survey, insert rest end point of federated feature service. (update form_id to that of the layer from service) 5. Receive Error. Alternatively: 1. Using the same federated feature service. 2. In Connect adding a new survey. 3. It creates the new survey with the correct schema but the submission URL is not the rest endpoint, its a feature service item description url. 4. Also when publishing I receive the same error as above.

‎06-05-2017

Gary, GeoEvent can be VERY frustrating. The properties look correct. I troubleshoot by recreating the inputs, reimporting the layer definition, deleting and recreating the service & checking logs to make sure connections are working.

‎05-17-2017

Can you use another field as the Where field instead of ObjectID when updating a feature?

Online Status	Offline
Date Last Visited	Tuesday

My Ideas

Latest Contributions by TL2

Re: Auto-populate Field With Next Number

Re: Troubeshoot GeoEvent Connection to Portal Issue

Troubeshoot GeoEvent Connection to Portal Issue

Re: water web isolation tool - Valve Classification and Barriers

Re: Can you set pooling for a hosted feature service (portal)?

Can you set pooling for a hosted feature service (portal)?

Re: How to update coded values of HFS published with Survey123 without overwriting service?

Convert VARBINARY (BLOB) to Base64 String using T-SQL

How to update coded values of HFS published with Survey123 without overwriting service?

Re: Sailing Around the World Release (2.2)

Re: Survey 123 & Federated Services: Clarification

Re: Survey 123 & Federated Services: Clarification

Survey 123 & Federated Services: Clarification

Re: GeoEvent Field Calculator to overwrite field.

Re: Can "update a feature - feature service" output connector updating some fields and leave others unchanged?

Create spatial view "by using a shape from another...

Re: Field Maps link - referenceContext=showFeature...

Re: Placeholder Image For Image Widget In Experien...

Re: Turn off pop ups for certain layers?

Re: Power BI and Survey123