Techniques and architectures for native data field lifecycle management

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 computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database, the one or more processors to:

maintain, in the data dictionary and with referential integrity in an environment belonging to a tenant owning data managed by the data dictionary, one or more custom database objects to provide metadata corresponding to the data dictionary, wherein the data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information, wherein the data dictionary identifies owners of fields and aligns fields across record types, and the fields are individually managed and provide field-level security, further wherein the fields provide data that describes one or more characteristics corresponding to objects stored in the database where standard fields exist for all objects of a particular type and custom fields associated with the object of the particular type provide additional attributes;

update, automatically in response to a field change, attribute information within the data dictionary corresponding to custom fields in either standard database objects or custom database objects;

provide data security at the field level by at least managing access at the field level based on user profile information; and

generate a notification to one or more users for one or more custom database objects that correspond to the data dictionary that cannot be updated automatically, if any, via a graphical user interface.

2. The non-transitory computer-readable medium of claim 1 wherein the custom database object comprises a fill rate indicates the percent of total records in which the field has been used.

3. The non-transitory computer-readable medium of claim 1 wherein the custom database object comprises an indication of one or more people responsible for the field.

4. The non-transitory computer-readable medium of claim 1 wherein the custom database object comprises an indication of a current status of the corresponding field.

5. The non-transitory computer-readable medium of claim 1 wherein the custom database object is created based on information received via a graphical user interface.

6. A method for maintaining a data dictionary within a computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database, the method comprising:

maintaining, in the data dictionary and with referential integrity in an environment belonging to a tenant owning data managed by the data dictionary, one or more custom database objects to provide metadata corresponding to the data dictionary, wherein the data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information, wherein the data dictionary identifies owners of fields and aligns fields across record types, and the fields are individually managed and provide field-level security, further wherein the fields provide data that describes one or more characteristics corresponding to objects stored in the database where standard fields exist for all objects of a particular type and custom fields associated with the object of the particular type provide additional attributes;

updating, automatically in response to a field change, attribute information within the data dictionary corresponding to custom fields in either standard database objects or custom database objects;

provide data security at the field level by at least managing access at the field level based on user profile information; and

generating a notification to one or more users for one or more custom database objects that correspond to the data dictionary that cannot be updated automatically, if any, via a graphical user interface.

7. The method of claim 6 wherein the custom database object comprises a fill rate indicates the percent of total records in which the field has been used.

8. The method of claim 6 wherein the custom database object comprises an indication of one or more people responsible for the field.

9. The method of claim 6 wherein the custom database object comprises an indication of a current status of the corresponding field.

10. The method of claim 6 wherein the custom database object is created based on information received via a graphical user interface.

11. A system comprising:

a memory device;

one or more hardware processors coupled with the memory device one or more processors configurable to maintain a data dictionary within a computing platform that provides a multitenant environment in which multiple tenants utilizing the multitenant environment share a single instance of a database, the one or more processors to maintain, in the data dictionary and with referential integrity in an environment belonging to a tenant owning data managed by the data dictionary, one or more custom database objects to provide metadata corresponding to the data dictionary, wherein the data dictionary tracks attributes for the custom database objects utilizing natively supported field attributes and the custom database objects maintain tenant-specific information, wherein the data dictionary identifies owners of fields and aligns fields across record types, and the fields are individually managed and provide field-level security, further wherein the fields provide data that describes one or more characteristics corresponding to objects stored in the database where standard fields exist for all objects of a particular type and custom fields associated with the object of the particular type provide additional attributes, to update, automatically in response to a field change, attribute information within the data dictionary corresponding to custom fields in either standard database objects or custom database objects, and to generate a notification to one or more users for one or more custom database objects that correspond to the data dictionary that cannot be updated automatically, if any, via a graphical user interface.

12. The system of claim 11 wherein the custom database object comprises a fill rate indicates the percent of total records in which the field has been used.

13. The system of claim 11 wherein the custom database object comprises an indication of one or more people responsible for the field.

14. The system of claim 11 wherein the custom database object comprises an indication of a current status of the corresponding field.

15. The system of claim 11 wherein the custom database object is created based on information received via a graphical user interface.

16. The non-transitory computer-readable medium of claim 1 wherein the data dictionary is utilized to manage personally identifiable information (PII) within the database environment.

17. The non-transitory computer-readable medium of claim 16 wherein the PII is utilized to manage field-level security functionality.

18. The method of claim 6 wherein the data dictionary is utilized to manage personally identifiable information (PII) within the database environment.

19. The system of claim 11 wherein the data dictionary is utilized to manage personally identifiable information (PII) within the database environment.

20. The system of claim 19 wherein the PII is utilized to manage field-level security functionality.