Could not find a table field

[tysonwenger]

Hi,

I made a couple minor changes to our Incident and Location forms in our Test env (added a couple fields and some basic UI Policy stuff).   I then went to move the update set from Test to Stage and I get these errors from the Preview Update:

1) Could not find a table field (incident.u_test_currency) referenced in this update
2) Could not find a table field (cmn_location.u_security_affiliate) referenced in this update
3) Could not find a table field (incident.u_age_of_ticket) referenced in this update      

It appears a developer before my time added these fields in the test environment, but not in the Stage or Prod evn.   I do not want these fields coming over since they are not related.

The weird thing is I never directly made any changes or references to those fields mentioned above, so I'm not sure why they came along in my update set.   Is it possible for this scenario to happen:

1)   Developer "A" creates an update set called "updateSetYY" that adds fields "fieldB" and "fieldC" to Incident table in Test env.

2)   Developer "B" creates an update set called "updateSetZZ" that adds fields "fieldD" and "fieldE" to Incident table in Test env.

3)   Developer "A" never migrates "updateSetYY" to Stage env.

4)   Developer "B" migrates "updateSetZZ" to Stage and receives errors about "fieldB" and "fieldC" even though he never added/or changed those fields in his update set.

I'm wondering if I should just skip those changes in my update set.

Thanks for any help!

[donnie5]

It is possible for the scenario you described to happen: something in your update set can reference fields you didn't add or change. If those fields are on the Incident and Location forms you are updating, then the XML representing those forms in the update set will contain references to those fields (not just the fields you added) and you will get the errors you received.

If the UI Policies in your update set are not new, you might want to check them for references to those fields as well.

[bernyalvarado]

Hi Tyson, if those fields are not supposed to be in the Stage or Production environments then you can just ignore the error by Accepting the remote update.

Thanks,

Berny

[tysonwenger]

Thanks Berny, I did end up ignoring those remote updates but I skipped them instead of accepting them.   As a result the fields that I created were not added to the form...     So the moral of the story is I should have accepted the update instead of skipping it correct?

But if I would have accepted the update would the other fields have been added that I didn't want?

Thanks,

-Tyson

[bernyalvarado]

Hi Tyson,

That's right. You should have accepted the updates instead of skipping them. Still, you just got wiser thanks to the experience and now you know better how it works.

If you will have accepted the update it would not have added the other fields because these do not exist on your environment. It will just have kept the reference in the record so that when the fields are added the relationship will be in place, unless a never update set overrides that relationship. In other words, if you will have accepted the change your accepted record will just hold the sys_id of the reference, but just that .

I hope this helps!

Please don't hesitate to ask if you have any further questions.

Thanks,

Berny