Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Exception on performing Search post migration

SA-95262

Summary



Exception occurs when user enters a few values and clicks the Search button post migrating from Pega 7.3.1 to Pega 8.2.4. 


Error Messages



Component stack mismatch {"NTId":"90264733740397","NTRef":"45c7594fc4731c85947c3f3ddd36d711b5c3332_130","pyName":"pxNonTemplate"}!!!!===={"liveUI":" data-ui-meta=\"{'type':'Container'}\" ","containerType":"NONE","isClientWhen":false,"pyName":"pxHarnessContainer","pyTemplates":[{"pzPrimaryPage":"TempSoDSearchPage","pxReferencedId":"edcc7dac72dafa296e80fb33db688b02096c8722_3","pyName":"pxSection"}]}


Steps to Reproduce



Unknown 


Root Cause



The section in which Component Mismatch exception occurs consists of a table with six columns. The source of the table is a pageList which refers to a Data page list and displays the results. Two columns out of six columns are configured to display a property which is present neither in pageList nor on data page. 

Resolution



Perform the following local-change:
Remove the undefined property from table.





 
Suggest Edit

Published December 9, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us