Portal views are badly implemented and designed. It is unlikely anyone is using them. The future of this is frappe/studio.
We are planning to remove this. Would love to know if anyone has a strong reason to keep them.
4 Likes
We have just started implementing them 
We have started utilising the portal views for Customers and Suppliers. Apart from few minor problems, these looks fine to us and are really helpful for us.
1 Like
Dear @rmehta, could you tell a bit more about frappe/studio? Are there a description, screenshots (if preliminary), a repo to preview?
Unless there is, you are asking a one-sided question. Which cannot really be evaluated because you lack the comparison, e.g. sufficient knowledge about the alternative. A cat-in-the-bag type of question.
Maybe a part of the portal devs and user will happily switch if presented with a well-integrated, dev-friendly app with a nice UI (or rather: UX, a term much more pragmatic) and a very simple, future-proof migration path for what devs already built and users already use.
It would also be nice to have a clean separation and communication path between backend (internal LAN) and frontend (www-visible portal). This helps keeping internals securely internal and not expose the whole data silo to a node accessible by default to third parties and potential attackers. Some degree of separation wouldn’t be a bad thing, would it?
One of the reasons we chose ERPnext over alternatives was the potential self service capabilities for customers through the portal. Turns out the lack of customization made them useless.
In our B2B case everything should be sorted by customer PO number, but that does not even show up on portal pages. Having a portal that we can customize the list view in terms of columns and order while all else is unchanged would help us be way more productive.