Share your ideas

Improvement for recurring data job functionality

Organization working with multiple datajobs and large number of WCA fields.

  • Guest
  • Feb 26 2020
How will this idea be used?

Hi WCA,
Currently, to make changes to a database, you must cancel all recurring import jobs for that database, update the database and fields, and then schedule the recurring job again.

If you rename the field and let the old data jobs run, it re-creates the field with old name in the database even though the data job doesn't update the concerned field.

Suggestion from WCA support was to try changing the field name after canceling these recurring jobs.

Can I make changes in a database while a recurring import is active?
https://www.ibm.com/support/knowledgecenter/en/SSWU4L/Data/imc_Data/Data_q_a_watson_assistant/Will_changes_in_a_Database_cause_a_Recur364.html


Impact:
It is not ideal and very time consuming having to recreate 3 data jobs after a single field being renamed in the database.

Suggestion would be:
- Firstly, the user would prefer the data job fail rather than WCA recreating fields that will prevent duplication of the field.
- Let the user just do the remapping within existing datajobs

- The best scenario would be - WCA updates the data jobs like it does for some other elements.



Thanks

What is your industry? Other
What is the idea priority? Medium