B2005p31 Validation Fail: Item Details

[ward_scott]

For us, this is the second critical function has failed validation. (If you missed it, the first is that proctored exams cannot be edited.) In this case, the drop down options in Item Details tab do not display. These include:

• Initial Basis
• Initial Period
• Initial Required Date Basis
• Retraining Basis
• Retraining Period

I have submitted a support ticket of course but I am just starting validation and, as is, am extremely uncomfortable with the issues I am finding. @sany said Please do what you can to postpone implementation. This release is not ready.

[may_thang]

please edit online content than go back to Item details and see if the dropdown lists are there as this is the issue and once you click on F5 to refresh the screen, the dropdown list reappears.

[PiotrPioro]

Hi Scott,

we are not experiencing these issues on our end - curricula details are there.

What is the probability that major release will be postponed? @sany said: is that something that you consider as an option?

Thx,

Piotr

[ward_scott]

This is not the curriculum. This is the Item Details "tab" of the item. These become the default settings for items in curricula when added. And, the Initial Period is the default when an Item is assigned directly to a user.

[Dhruv]

I can see the drop down just fine in our validated stage instance. Is this issue local or global?

[jorgecampos]

I encountered this behavior after deleting an online content. I plan on testing whether edits or removals on other tab cause the behavior.

[may_thang]

I have the same issue with Item Details. If I modify the online content tab then went to the Item Details, I get the issue Scott mention were the dropdowns are blank. Then I searched for the same item and opened it again and they were all back. There's definitely an issue however it seems to go away when you refresh the item i.e. F5 on browser works as well. Regards, May

[ward_scott]

That does seem to work, although I wish I had more time to investigate thoroughly.

[may_thang]

This was the concern I had with patch 31 getting released so close to go live date. This issue still needs to be fixed however I don't know what is the root cause and could it be worst with bug fix as p31 should not have any impact especially since we did not have any issues with curriculum details not appearing...sigh

[Maria_Molvin]

Do all of you have Patch 31 in Sandbox and Stage? I looked and it shows Patch 31 uploaded on 11/28 in Sandbox, but not in Stage. Is anyone else seeing this?

[ward_scott]

We have patch 31 in Staging.  Ours was applied on 11/27/2020 10:34 PM America/Chicago.

[Sany-Said]

Hi @ward scott , thank you for raising the issue you're experiencing. At this time there are no plans to delay the Production upgrade from its current date.  We will assess the issue you raised and remediate accordingly based on the issue triage and workaround availability. We can certainly prioritize this and any other high level concerns for the next upcoming patch as planned.

[SSimms]

Hi Ward,

I just tested this scenario in our Preview / Sandbox, and I do not have this issue. Our drop-down lists have values.

Stephanie Simms

[may_thang]

please edit online content than go back to Item details and see if the dropdown lists are there as this is the issue and once you click on F5 to refresh the screen, the dropdown list reappears.

[ward_scott]

I can now reliably make the page fail and a refresh (F5) has always been successful.

[SSimms]

Just confirming that our team was able to replicate this issue in our environment, and hitting F5 / Refresh is a workaround that lets us see the missing drop-down values.

This issue also appears for the drop-down choices related to automated attendance capture on items / classes with VLS integration enabled. F5 allows the values to be visible. 

Awaiting a fix. Tyou.

[may_thang]

Does anyone know if this will be fixed with patch 32? I had a case open and they told me the fix is in b2105 which then it wouldn't be until the end of the year.
Thanks, May

[ward_scott]

The issue still exists. We failed our test case but included a comment that a workaround was identified in the previous validation.