Techniques and architectures for data field lifecycle management
Data field lifecycle management mechanisms. Custom metadata about a database object is generated. The custom metadata includes at least a specified name for the custom metadata type, a specified one or more fields to contain configuration information for the custom metadata type, and specification of at least one relationship field having fields as its domain relating the custom metadata type to a column or field of the database object stored in a database. One or more objects of the custom metadata type are maintained with referential integrity to provide metadata corresponding to the database object. The custom metadata objects maintain tenant-specific information. The one or more objects of the custom metadata type are updated automatically. A notification to one or more users is generated for one or more objects of the custom metadata type that cannot be updated automatically, if any.
1. A non-transitory computer-readable medium having stored thereon instructions that when executed by one or more processors, are configurable to cause the one or more processors to:
maintain a data dictionary within a multitenant computing system in which multiple tenants share a single instance of a database, the data dictionary being stored and maintained within an area of the multitenant computing system accessible to a tenant associated with data managed by the data dictionary
generate custom metadata about a database object associated with the tenant, wherein the database object has corresponding objects within the area of the system accessible to the tenant, wherein the custom metadata describes one or more relationships with other data, the custom metadata is specific to the tenant, and the custom metadata is in addition to standard metadata for the database object;
generate one or more custom metadata types based on the custom metadata, wherein the data dictionary maintains:
a connection between selected custom metadata types and a file utilizing the selected custom metadata types;
upon receiving an update to the custom metadata, update, automatically, one or more objects of the custom metadata types within the data dictionary, wherein a database object has corresponding objects in at least two different sandboxes within the multitenant computing system; and
generate a notification to one or more users for objects of the custom metadata types within the data dictionary that cannot be updated automatically, if any.
2. The non-transitory computer-readable medium of claim 1 , wherein the custom metadata comprises an indication of one or more people responsible for a field.
3. The non-transitory computer-readable medium of claim 1 , wherein the custom metadata comprises an indication of a current status of a corresponding field.
4. The non-transitory computer-readable medium of claim 1 , wherein the custom metadata types can describe relationships with other data, but can only be used to look up metadata and not data.
5. The non-transitory computer-readable medium of claim 1 , wherein the custom metadata objects comprise at least a fill rate that indicates a percent of total records in which a field has been used.
6. The non-statutory computer-readable medium of claim 1 , wherein the custom metadata types correspond to record fields.
7. A method comprising:
maintaining a data dictionary within a multitenant computing system in which multiple tenants share a single instance of a database, the data dictionary being stored and maintained within an area of the multitenant computing system accessible to a tenant associated with data managed by the data dictionary;
generating custom metadata about a database object, wherein the database object has corresponding objects in at least two sandboxes within the environment belonging to the tenant, wherein the custom metadata types describe relationships with other data and the custom metadata types are specific to the tenant and in addition to standard metadata for the database object;
generating one or more custom metadata types based on the custom metadata, wherein the data dictionary maintains:
a connection between selected custom metadata types and a file utilizing the selected custom metadata types;
updating, automatically, one or more objects of the custom metadata types within the data dictionary, wherein a database object has corresponding objects in at least two different sandboxes within the multitenant computing system; and
generating a notification to one or more users for objects of the custom metadata types within the data dictionary that cannot be updated automatically, if any.
8. The method of claim 7 , wherein the custom metadata comprises an indication of one or more people responsible for a field.
9. The method of claim 7 , wherein the custom metadata comprises an indication of a current status of a corresponding field.
10. The method of claim 7 , wherein the custom metadata types can describe relationships with other data, but can only be used to look up metadata and not data.
11. The method of claim 7 , wherein the custom metadata objects comprise at least a fill rate that indicates a percent of total records in which a field has been used.
12. The method of claim 7 , wherein the custom metadata types correspond to record fields.
13. A system, comprising: at least one memory device;
one or more hardware processors configurable to:
maintain a data dictionary within a multitenant computing system in which multiple tenants share a single instance of a database, the data dictionary being stored and maintained within an area of the multitenant computing system accessible to a tenant associated with data managed by the data dictionary;
generate custom metadata about a database object associated with the tenant, wherein the database object has corresponding objects within the area of the system accessible to the tenant, wherein the custom metadata describes one or more relationships with other data, the custom metadata is specific to the tenant, and the custom metadata is in addition to standard metadata for the database object;
generate one or more custom metadata types based on the custom metadata, wherein the data dictionary maintains:
a connection between selected custom metadata types and a file utilizing the selected custom metadata types;
upon receiving an update to the custom metadata, update, automatically, one or more objects of the custom metadata types within the data dictionary, wherein a database object has corresponding objects in at least two different sandboxes within the multitenant computing system; and
generate a notification to one or more users for objects of the custom metadata types within the data dictionary that cannot be updated automatically, if any.
14. The system of claim 13 , wherein the custom metadata comprises an indication of one or more people responsible for a field.
15. The system of claim 13 , wherein the custom metadata comprises an indication of a current status of a corresponding field.
16. The system of claim 13 , wherein the custom metadata types can describe relationships with other data, but can only be used to look up metadata and not data.
17. The system of claim 13 , wherein the custom metadata objects comprise at least a fill rate that indicates a percent of total records in which a field has been used.
18. The system of claim 13 , wherein the custom metadata types correspond to record fields.