Force Table to update set

[Ken83]

Hello Community,

        I'll preface all of this by saying that I'm running the latest patch of Eureka on all of my instances. So the problem that I've run into is forcing a table into an update set. I was in an Update Set when i created the table but when I move the update set to my QA instance, it's generating errors because it cannot find table fields which existed on the table right after it was created. The obvious thing to check is the "Force to Update Set" UI Action and it just tells me that updates are already being recorded for the table in question. Has anyone else had this problem and have any fixes for it? My goal is to simply move the update set that the table was created in, to another instance and have the table and it's associated fields show up.

[Brad Tilton · Accepted solution]

Have you actually committed the update set or are the errors in the preview? I've had issues with the previews finding errors that were related to other records in the same update set. You could also just open a new update set and update the dictionary records so they get tracked to your new update set.

[Ken83]

These were in the preview of the update set. I went ahead and moved the update set and to my surprise everything was there so now i'm even more confused as to why it generated the errors.