Need Non-Automated Inquiry Assistance re: Field Type error in Academy Mission Exercise Module
I need human intervention, Please.
In the Pega Academy instance... I made an error in Low-Code App Builder Mission exercise "US-005: Review Transfers view" by formatting a view field as text instead of as currency. I need to know ASAP if I need to reset my Pega Instance and start over or if this error can be fixed so that I can proceed. I have already requested help 3x and keep getting automated replies that do not provide any helpful guidance. I cannot afford to waste time moving forward if I need to reset and start again.
- I tried deleting the field and recreating it with the same name but I get an error saying the object already exists.
- I tried creating a new field name similar to the expected object name and formatted it correctly.
In the first case the form correctly processes but the value is displayed as a decimal instead of as currency. In the 2nd case the form correctly processes and displays the value as currency as expected. In each case the flow works but I get an error at verification of the exercise, first indicating the formatting error and 2nd not finding the expected object name (because I could not keep the "old" name and had to give the new object a different name.
Please PLEASE can a human review this and offer some guidance that I can use?
Steve Delaney
Accepted Solution
Updated: 22 Aug 2022 10:45 EDT
Pegasystems Inc.
US
@SMDELANEY Hi Steve, I recommend reviewing the FAQs for challenges and mission exercises. It takes a little bit of know-how to correctly fix your issues. For example, you cannot change a field (property) type. You have to delete the existing field (property) then create a new one. If you are removing the field from the view you are doing just that - removing the field from that view - but you did not delete the field (property).
The issue regarding not finding the object name is also noted in the FAQs. The auto-grader is checking for the specific name as specified in the acceptance criteria. Any other name does not meet the acceptance criteria, so your solution build will not pass validation. The FAQs guide you through the process for fixing this error; here as well, it takes a bit of know-how to correctly delete a data object and create a new one in its place.
As we mentioned in our response in the CDP Support email channel, your options seem to be to review the FAQs and try to fix your mistakes - so the user stories pass validation - or reset the Pega instance and try building a solution for the mission exercise, taking care not to make the same mistakes again.
I logged onto your system and, based on my review, my recommendation is to reset the Pega instance. You will spend more time trying to unwind your mistakes than just starting from scratch.
IBM
US
@eddie.jmThank you. In the end I did reset my Pega Session and start over precsely because I figured out it would take longer to fix it than to start again from scratch.