Mailing list spreadsheet is empty. This was news to me today

Justin Kraemer

August 15, 2018 15:19

I use the Mailing List Export to Excel workflow as a reference workflow to the Complete Parcel Selection, Buffering, and Report Workflow I obtained in the code gallery here. Until recently the setup has worked very well.

 

Sadly I learned today it no longer does.

 

What I have is two versions of the Mailing List Export to Excel tied to two buttons in the calling workflow named above. The output Excel spreadsheet from one of them is empty but for its column headings. From the other it comes up the same but for one column being populated while the rest are empty. I wonder why that column works in one and not the other, and why the rest are blank in both.

 

Can someone please explain why this might be? For relevant background, I had to move the SDE database to a new server in the past two weeks and republish all map services to point to the new database connection. Before this task I know the workflows were last run successfully. I have a secretary needing to create mailing lists today, and that's how I learned of the problem.

 

Please help.

 

Thanks,

 

Justin

 

 

 

0

• 

  Permanently deleted user

  November 15, 2018 23:22

  Hi Justin,

   

  Your new SDE data may have ended up with a different schema.  This can also happen when you introduce a table join into existing data.  In this case, the fields become fully qualified, e.g. what used to be ADDRESS is now USER.SCHEMA.ADDRESS.

   

  Other times, the data migration will introduce new fields (OBJECTID becomes OBJECTID_1 or FID).

   

  Both things can break a workflow that relies on fields having specific names, data types, or ordering.  I would check over your workflow and workflow configuration and verify that any fields in there match up to what they're published as now.

   

  Regards,

   

  -Malcolm

  0
• 

  Justin Kraemer

  November 16, 2018 14:15

  Thanks for your reply, Malcolm. I regret that I overlooked posting here what I did to solve the problem. 

   

  It was caused by the way in which I had republished the map services to point to the new server. What I found at fault was that I had recreated the join through a different database user name. Upon changing the join back to how it was before and republishing the service, the problem went away.

  0

Please sign in to leave a comment.