The complex schema in the new UI is having issues rendering nested schema (array -> record -> basic types) in that order.
Steps to reproduce:
1. Deploy PurchaseHistory app
2. history dataset should get created.
3. Click on history entity card in the home page
4. Switch to schema tab.
The schema tab looks empty and the UI fails with a js error. The reason being we are doing incorrect parsing while rendering a complex array field (meaning array of records).
The fix should be to use the right parsing logic (use cdapavsc.parse) instead of using the parser function in the SchemaHelper