Update set changes to Record Producer not carried through to production

[will_smith]

I made some changes to a record producer update set in Dev yesterday and when I rolled it out to production the script was not the most current, and a second record producer I had created, and then inactivated, was active. Would someone help me understand why? This is the 2nd time this has happened - active states flipping; not with a record producer though.

[Goran WitchDoc]

Hi shrikanth,

I sadly never used data sources myself to be honest. The few times we needed to move data from one instance to another we did it just by going to the table, rightclick and export to xml, then on the other instance we import it. Otherwise we get the data from production by cloning, which we do pretty often. We do that after each new release which is about once a month.

[Nani6]

Hi Goran,

No Problem, Thanks for your reply.

[will_smith]

Let me check. That's the other thing I don't understand, if the default update set is always In Progress, how does it get transferred over to production? Is that in the update retrieval process?

[Nani6]

Hi William,

Please create a new update set and capture your changes in the new set, then move this update set to Production.

Note:- while creating new set, don't forget to check the default update set field.

[Goran WitchDoc]

ERgh.. Stuff in default doesn't get moves between the instances, just because as you say, it is in progress.. even if you would completed and manage to retrieve it in next. Don't even know if you can complete default =).

But then, you must manually go to production and and commit default, which I really hope you haven't done 😃