Joshua Pack

It doesn't seem possible to make custom fields on the Organization object mandatory.  I've gone through the documentation and this looks like it used to be possible in the ‘Business Rules’ area, but not any longer.  Am I missing something?

Ashwin Raju I actually have the same issue that Guilherme has (sorry didn't realize there were 5 pages of comments).  

My company is doing B2B support.  We are using a Organization drop down lookup to identify the customer on a given issue.  This is being done because the party that opens the ticket may not be with the actual organization.  Our support is handled by our internal employees, 3rd party contractors and the organization itself.  Using an organization drop down allows us to correctly identify who the requestor is, and but connect the reported issue to the correct organization. 

The challenge is that the lookup does not add the organization tag to the ticket as expected.  Our customers would like to see all tickets opened for their facility, but tickets opened by a requestor that is not in that organization doesn't add the necessary tag for a ticket to show up in the Help Center portal. 

Is there a way to create a trigger to add the organization tag from the lookup field?  It would be wildly helpful for us. 

Thank you in advance. 

This remains an issue for our company where we have different organizations that are part of a broader account and all use the same email domain, so we cannot automatically add Org tags to endusers who register themselves. 

What would be super helpful is a simple trigger that anytime a new email address/user joins the Help Center and registers, a support ticket is generated to notify our help desk team so the contact can be verified and tagged.  That would provide a quick and easy way to verify who is registering for our system, and grant them the access they require to access what they need.