Advanced Request Offering not appearing in portal
Hi
I edited an advanced request offering in our dev instance and the changes to the offering weren't flowing through from the service manager console to the Cireson portal even after recycling app pools, restarting the website, clearing the health service state folder and restarting the Cireson cachebuilder service. I then checked the cachebuilder log and saw this error
ERROR [ 21]: GetRequestOfferingRow failed with error: Object reference not set to an instance of an object.
I then followed the instructions on this page:
And now the advanced request offering doesn't show in the portal at all!
Answers
Hi all, good news!. With @Brett_Moffett2 pointing me in the right direction. Someone had removed a prompt from the ARO but in the XML of the ARO, the layout section still had a reference to the removed prompt which was the cause of the "GetRequestOfferingRow failed with error: Object reference not set to an instance of an object." error message in the cachebuilder log.
@Dean_Mrazek with a little bit of PowerShell we could create a ARO Validator that would look at all the references in a RO and check that they all exist.
I'd never thought of removal of a property from the ARO itself would cause this, but it makes sense when I stopped to think about it.
Maybe this ARO Validator is a sideline project for the Systematech or Cireson teams. :)