I’m trying to configure HCMS webpages. While creating one I encountered an error that keeps popping up everytime I open a HCMS web page, both after pressing the + to create one all the way through finishing setting it up.
I’ve checked everything and all should be well, but still the error keeps popping up. I’ve configured a website to use the URL, configured webpages according to another application I use as an example. Everything that could be active is active and the only things that are empty are things my example also keeps empty.
This looks suspicious if you get this while active is clearly checked. Which suggests the issue might lie somewhere else.
The best way to figure this out would be to perform a trace, so you can pinpoint which active field it is talking about.
OR maybe it already provides more info if you put ?__setShowVerboseErrorMessages=true behind your application URL.
Can you share the validation message from the trace or verbose message? This should provide info about the specific record it is looking at that has an active field.
(It could for example be the active field of the user).
You should use the “Process” trace element.
And somewhere in the trace log there should be a mention of “FailedValidationsMessage”.
Which should include the record for which the validation fails.
f.e. users:load(1)
That’s record the validation fails for, which should help you fix it (by making it active).
you can’t have two question marks in the URL. The /? must be replaced by &
So: default.aspx?__testmode=true&__setShowVerboseErrorMessages=true
This will highly likely provide you with the exact record type that throws the error.
Most likely, a data process will try to add/edit another record with a validation error. With the setShowVerbose, the system will tell you which record.
Which version of the HCMS component are you using?
Now that we know the record that is causing the issue, namely: users:load(1) we can fix the issue.
The reason for the validation error should be easily testable by going to that user record. Click ‘Edit’ > then click ‘save’ >> The result should be a validation error for is_active.
This is not something that happens often, but it might be the case that trial applications have an Administrator and Webservice account where the is_active = NULL.
The fix: Edit the user record with id=1 (Administrator) and set active to true.
Note: Might as well do the same for id=2 (Webservice)
– Background info:
In the component there is functionality build in that provides the preview of the webpage in a certain way. This is based on a setting found in the Settings menu: Web page preview settings.
This setting can be configured per user. And the process mentioned in the screenshot sets this setting based on the default one (or based on the one chosen one) at the user record.
