Edit the create form to include any associations to your custom object

Joshua Oakes read the why-it-matters and welcomed it, “which is fantastic,” then made the bigger point: “any day now, custom objects will be just like real objects.” He sized it this way: “They are more real than the lead object, but not quite as real as first class…”

Why it took this long, in his telling: “They had previously been considered out of flow.” He said, “I don't know if this is the mindset, but the UI was telling you, oh, you don't create a custom object. You go to the deal or the customer or the company, and then you start the process from there.” In his own client work it has not looked that way. Custom objects have often been their own element, a work object where a process or record runs natively on the custom object as a core pillar of the business, and “the UI was just not treating it that way.” He described the old picture, the real work on deals, contacts and companies with custom objects bolted on, against custom objects now able to represent a core element of the business.

Chris Carolan brought in the Pro question. He raised custom objects coming down to Pro, said it is being tested in other parts of the world right now, and said you can't have a gap like this once they do. His own guess for why it was not a priority: “I imagine it wasn't a priority because of the way that custom objects generally get used as just a place to store specific data and not really a part of any active user process…” For now the panel names Enterprise on every hub it lists.