Featureset from Buffer and fields from datalink

Permanently deleted user

8. März 2014 09:40

I am having a bit of a problem.

I am doing a typical workflow for 'select parcel, then buffer, and send results to excel file'.  This is working correctly, except I am wanting to export fields on the parcel layer that are connected using a data link query into a database.  I can't seem to access these fields from the 'Out' fields of the query without an error.

Is there an extra workflow step I need to add to get these fields?

The strange thing is that in the results list (after the buffer is done) shows the parcel layer fields, and after a few seconds (once the query finishes), the columns are added for the datalink fields.  So the datalink is working correctly.

Any suggestions would be much appreciated.

 

Cheers!

0

• 

  Permanently deleted user

  12. März 2014 08:58

  No thoughts/ideas on this one from anyone?

  Hopefully I have worded my issue correctly.

  I was hoping it would be an easy answer.  I was presuming that lots of people would have run into this same issue (accessing fields from a datalink).

  Thanks!

  0
• 

  Permanently deleted user

  12. März 2014 22:54

  Hi Bret,

  The data link results are collected by the viewer at display time and won't be available to a Query Task.  The Query Task only gets data from ArcGIS Server, not from Essentials, so adding "datalink.field" to the out fields will not work.

  There are Sql Query activities that you can use to make a new connection to your database from workflow.  This activity returns a DataTable.

  The Merge DataTable activity should help you push the data from the SQL query into the featureset (you'll have to use Featureset to DataTable first to get a merge target).  That's for one-to-one data links.  For one-to-many, add the resulting DataTable to a DataSet and use the DataSet to XLS activity to generate your Excel document.

  Regards,

  -Malcolm

  0
• 

  Permanently deleted user

  13. März 2014 01:34

  Thanks for the response Malcolm.

  I will try this on a future workflow.  I ended up just doing the join at the ArcGIS level, and published the service with the database connection and extra fields at that point.

  Cheers!

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.