Build your application with custom objects

When you create a custom application, you also need to create objects to receive and process the data needed within it. Any distinct information record that's cardinally different from another record needs an object to handle that record type. For example, Invoice is one object and Invoice Line Item is another object.

Objects are made up of components that define how Sage Intacct manages and processes the object's data records. Components can include fields, relationships, pages, list views, email templates, document templates, triggers, workflow processes, data maps, and unique indexes. These components apply to the object records in scope. For example, you might create a Collections Activity object to hold records about calls and emails for collections. When you do, the automated activities, like status changes and record updates related to the object, are set up as part of the object definition.

You can also create an object to hold certain application settings. For example, in a Collections application, you can have a Collections Activity object that holds all the call and email records. Or you might have a Collections Settings object to hold information like the return email address and remittance details for automated notifications.

Objects exist independently from applications and can be assigned to several at the same time. When creating an object, plan how the object will relate to other objects used by your application. Know if you need one-to-one, many-to-one, or many-to-many relationships with other applications.

Do you want more help with your development work? Explore and get answers from other users by visiting the Sage Intacct Developers Club. Sign in to learn more, or create an account now.