WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts > Forms

Forms

Please check this code.

To show:

const divs = document.querySelectorAll('.table-tree');

divs.forEach(div => {
const uls = div.querySelectorAll('ul');

uls.forEach((ul, index) => {
if (index > 0) {
ul.classList.remove('hidden');
}
});
});

To hide:

const divs = document.querySelectorAll('.table-tree');

divs.forEach(div => {
const uls = div.querySelectorAll('ul');

uls.forEach((ul, index) => {
if (index > 0) {
ul.classList.add('hidden');
}
});
});

MVP

Hi Raluca,

as far as I can tell the display name is not always resolved and in the DB only the ID is stored. I don't know when it happens but there are some cases.
When the workflow instance is then displayed in the form, the fields are "recalculated" and if you hit save, the data may be updated.
This doesn't happen in the report.
The reason why you see the id in the report at all is, that starting with BPS 2023 the rules/logic was changed so that any value in a choice field without a # is interpreted as the displayname.

At least this is my assumptions based on my experience in a similar case.
I had a lengthy discussions about this whole change to how the rules and the calculated_id field works to no avail.

Best regards,
Daniel

MVP

Hi,
I encountered the following error.
I have an action that sets a value in a choice field.
I set the choice field through the value of the ID.
When I enter the form, the value is correctly set, and it displays the name corresponding to the set ID.
However, when I enter the report, in that column, I see the value of the ID instead of the name. I tested by setting the value in the choice field as follows: id#name, and I no longer encountered the problem.
Why does it behave differently in the report when filling out the choice field through the value of the ID?

Thanks,
Raluca