How to save the field content for later? ax2012 x++

(0) Share

Report

Posted on by Tom Fi

I create a job in x ++. I would like the dialogfields inside the dialog to remember what the user entered for later (until the next Job launch)
How to do it?
Does Ax2012 have mechanisms to remember user variables?
Or do I need to write values to files on disk, or to the windows registry?

Best regards
Tom

I have the same question (0)

All responses (7)

Answers (0)

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Tom,

Assuming you are talking about X++ job, I don't think you can save the last values.

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (1)

Report

You should use RunBase or SysOperation framework, then the last values are stored automatically.

Check class Tutorial_RunBaseBatch.

Was this reply helpful? Yes No
Tom Fi 15 on at

Like (0)

Report
DialogRunbase dlg; DialogField txtDim, lstWorker; dlg = new Dialog("Title"); txtDim = dlg.addField(extendedTypeStr(Comments_JP), "Parameters"); lstWorker = dlg.addField(extendedTypeStr(HcmWorkerRecId), "Select worker"); dlg.run();

I made DialogRunbase like this.
It doesn't remember the values the next time it is started
What is missing?

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

Did you find the tutorial class? Pay attention to the CurrentList macro in class declaration (define list of variables to be stored), as well as pack (saving values) and unpack (fetching old values) methods.

Was this reply helpful? Yes No
Tom Fi 15 on at

Like (1)

Report
I didn't understand this part and missed it.
Now I understand a little, but does it all only work inside classes?

[SOLVED

I made progress and found another solution using xSysLastValue.

I present a solution for other interested people:

DialogRunbase dlg; DialogField txtDim, lstWorker; container conValues; dlg = new Dialog("Title"); txtDim = dlg.addField(extendedTypeStr(Comments_JP), "Parameters"); lstWorker = dlg.addField(extendedTypeStr(HcmWorkerRecId), "Select worker"); conValues = xSysLastValue::getValue(curExt(), curUserId(), UtilElementType::Job, "SaveLastValue"); if (conValues != conNull()) { txtDim.value(conPeek(conValues, 1)); lstWorker.value(conPeek(conValues, 2)); } if (dlg.run()) { conValues = conNull(); conValues = txtDim.value(); conValues = lstWorker.value(); xSysLastValue::putValue(conValues, curExt(), curUserId(), UtilElementType::Job, "SaveLastValue"); }

It works ok

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

Yes, it only works in a class because you need to extend RunBase. Why are you using a job for something that is executed often? You should develop a class, link it to a menu item, menu, security and so on. Jobs are not intended for implementing actual business operations.

Was this reply helpful? Yes No
Tom Fi 15 on at

Like (0)

Report

Good point of view. I will think about it next time

This code is for the IT department only. It has historically been a practice in the IT department to use Jobs to automate activities. It has remained so far

Thank you for replies :)

Was this reply helpful? Yes No

Join the conversation

Community site session details

How to save the field content for later? ax2012 x++

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

How to save the field content for later? ax2012 x++

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