Some Dev changes are not reflected on UAT environment

(0) Share

Report

Posted on by MDeeb

Hi All,

we did some development on dev envionrment but they are not reflected on UAT environment , what would be the issue ?

Thank you,

I have the same question (0)

All responses (12)

Answers (1)

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi,

when you do development, it only impacts the local objects on the development server.

You should check all the steps between the developer and the UAT system (such as DEV branch, MAIN branch, build pipeline..) to figure it out.

Was this reply helpful? Yes No
AnithaEswaran 2,032 on at

Like (0)

Report

Hi Mohammed,

Are you using Pipeline to deploy the changes to UAT? If it is pipeline, then please check if you changes are checked in . If it is a manual package creation, the environment from which you created the package , should have performed the 'Get Latest' .

Was this reply helpful? Yes No
MDeeb 92 on at

Like (0)

Report

Thank You Nikolaos.

actually we are just creating package from dev and then uploading it to LCS then applying to the environment.

Was this reply helpful? Yes No
MDeeb 92 on at

Like (0)

Report

Thank You Anitha.

actually we are just creating package from dev and then uploading it to LCS then applying to the environment.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi,

if you created the package directly in the dev system (which you should NOT) do, then the changes in all models that you included are definetely deployed to UAT system.

Could you please explain what you mean by "not reflected on UAT environment"? This seems to mean something else than "not deployed to UAT environment".

It would be nice if you could share all details about the issue - including exact explanation of expected and actual situation, screenshots, code...

By the way, I very strongly suggest you to change your deployment process. Otherwise you will almost certainly run into issues such as losing your source code, not being able to fix issues in your prod system etc.

At least be sure that the decision makers of your customer are aware of the current risks and accept them.

Was this reply helpful? Yes No
MDeeb 92 on at

Like (0)

Report

Thanks a lot Nikolaos,

what actually is not moved is the logic that for examples that locks some buttons when workflow is completed, those changes were not moved, however it is working on development.

as for the changing deployment process, we have only dev machine, may you please share the process of using the build automation ?

Thank you,

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Hi,

"changes are not working" and "changes were not moved" are two different things. The fact that this is not working in your test system doesn't meant that it was not deployed. For sure it's still possible that your changes weren't included in the package that you created in the dev system. But it's impossible to tell based on the facts that we know.

If you have correctly shared all the details with us, I would say that your changes were deployed. And your problem is caused by something else. If you still need help, please share all the information that I requested in my previous message. Until that I can't really provide better help.

Regarding the deployment process, I recommend to read everything here: ariste.info/.../

Was this reply helpful? Yes No
MDeeb 92 on at

Like (0)

Report

Thanks a lot Nikoloas,

below is the code that was not reflected on UAT, it is custom form which has the below code on active method :

if(EOSOverallPayment.WorkflowState != TradeWorkflowState::NotSubmitted)

{

EOSOverallPayment_ds.allowEdit(false);

EOS.enabled(false);

RetirementPayment.enabled(false);

PendingPayments1.enabled(false);

PendingDeductions1.enabled(false);

VacationsBalance1.enabled(false);

}

else

{

EOSOverallPayment_ds.allowEdit(true);

EOS.enabled(true);

RetirementPayment.enabled(true);

PendingPayments1.enabled(true);

PendingDeductions1.enabled(true);

VacationsBalance1.enabled(true);

}

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

Thanks.

You just have to double check that you really created the package from latest code (and correct models). If you did, and if you deployed it succesfully to your UAT system, then the code is in the UAT system.

Once you're sure that the code is in the UAT system, you can start looking at the data, or debugging to understand the issue better.

Perhaps the EOSOverallPayment.WorkflowState is not what you assume it to be.

I think I've given all the inputs that I have, but I'm sure you can find the explanation by following these instructions.

Once you have proper build&deployment process in place, you can always be 100% sure what code is deployed.

Was this reply helpful? Yes No
MDeeb 92 on at

Like (0)

Report

Thank you so much Nikolaos,

but what does it matter if we have created the package from the build env that we have or did it though devops, isnt it the same but the difference is automation ?

Thank you,

Was this reply helpful? Yes No

Join the conversation

Community site session details

Some Dev changes are not reflected on UAT environment

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Some Dev changes are not reflected on UAT environment

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates