How can we use relate field or relationship field in case create in Sugar Portal

Hi Juned Rawoot ,

I agree with Chris Raffle , relationship in portal requires code customization, even more because the modules are probably not availables for the portal.
There was an article that is relate to that : Adding a Custom Module to the Customer Portal 

But be aware that your customer won't be limited to "his" records (it wil require more code customisation).

Recently, we use the enum-api code instead of display the field as a relationship field : https://github.com/LampadaGlobal/enum-api

That way, you can easily set up a query to restrict the available record that can be selected and it will fill the relationship for your users in the CRM.

Hope it helps,

Fred

Hi Juned Rawoot ,

I agree with Chris Raffle , relationship in portal requires code customization, even more because the modules are probably not availables for the portal.
There was an article that is relate to that : Adding a Custom Module to the Customer Portal 

But be aware that your customer won't be limited to "his" records (it wil require more code customisation).

Recently, we use the enum-api code instead of display the field as a relationship field : https://github.com/LampadaGlobal/enum-api

That way, you can easily set up a query to restrict the available record that can be selected and it will fill the relationship for your users in the CRM.

Hope it helps,

Fred

Thank you for sharring your experience with enum-api, Frédéric Rinaldi , we appreciate it!

Definitely any feature inside Customer Portal requires customization but it is easy to explore the SugarCRM framework to incorporate in there some core features like Visibility Strategies, endpoints, subpanels, filters, dashboards etc.

Recently we incorporate an exciting feature which publish to Customer Portal a set of reports which render under Sidecar framework, giving portal users the hability to modify runtime filters and export as csv/pdf just like regular users do from inside Sugar. Portal users loved it once they are able to follow sla allocation/metrics/kpis without needing to ask backoffice users.