Customers-Contacts Application is built.
Customers list is as following.
Contacts list is as following.
Customers referenced in Contacts list are represented with numbers (i.e. Customer_id of Customer)
Meaningful Identifier is required for customer in Contacts list.
Custom Identifier is created with Customer-Name for Customers list.
Custom Identifier is created with Contact-Name for Contacts list.
Better custom Identifier is created with for Customers list.
Better custom Identifier is created with for Contacts list.
Some Fields/Columns of Customers list can be now kept hidden because of better Customer Identifier.
Some Fields/Columns of Contacts list can be now kept hidden because of better Contact Identifier.
The most recent update is maintained at Custom Identifier Spreadsheet Table Records
You can keep certain sensitive data e.g. Social Security Number encrypted.
First group of people do not have access to decrypted Social Security Number.
Second group of people(e.g. Customer Support) have access to last 4 digits of Social Security Number.
Third group of people(e.g. Admin) have access to full decrypted Social Security Number.
The latest document is maintained at MyDataOrganizer_Encrypt_Decrypt_Sensitive_Data .
You would like to design basic customers and contacts application.
Prepare basic info. in spreadsheet format about customers and contacts like the following.
As you can see there is repeated data about customer name.
Customer Microsoft is repeated twice.
Customer Oracle is repeated three times.
You are managing Customers and Contacts.
You will make one table(table = spreadsheet ) for repeated data.
So there will be one table for Customers.
Data in the Customers table will be as following.
Structure of Customers table is as following.
Field/Column Customers_1_id will be maintained automatically by the system.
Please note that other features about Customers
e.g. Customer-Industry, Customer-Address etc. can be easily added at later time.
The rest which is left is Contacts.
Contacts-table will have link to Customers-table.
Data in the Contacts table will be as following.
Structure of Contacts table is as following.
Field/Column Contacts_1_id will be maintained automatically by the system.
Please note that there is link to Customers in structure of Contacts.
The link to customers will force to have a customer for each contact.
Please note that other features about Contacts
e.g. Contact-Phone-Numbers, Contact-Title etc. can be easily added at later time.
The latest document can be found at MyDataOrganizer_Design_Customers_Contacts_Application
Spreadsheet style interface has color coded fields e.g. blue and green.
Blue color fields can be modified by people belonging to blue group.
Blue Group has read access to all the fields.
Green color fields can be modified by people belonging to Green group.
Green Group has read access to all the fields.
People belonging to Admin Group has full access to modification of all fields.
The latest updates to this document can be found at MyDataOrganizer_TeamCollaboration_SpreadsheetStyle_ColorCodedFields
Spreadsheets vs Web-Applications using Online Database
Human Resources Department can have access to Salary Info of Employees.
Other Departments can have access to info about Employees other than Salary.
There are many chances of manual errors while using spreadsheets and
can result into duplicate records, incorrect financial calculations etc.
There are many versions of the same spreadsheet which are mailed back and forth
and it is difficult to keep track of it. Web Application provides central location
for all the data which is available anywhere, anytime.
Working in a team environment it is possible to email wrong version or miss
sending attachment to team member. Web application provides the latest
data for all team members so there is no confusion.
Spreadsheet can not be used to store sensitive information like social security number
etc. because it is stored in plain text. Web Application can store data
encrypted and can provide access to decrypted data only to authorized team members.
Team members who should not have access to decrypted information can
only see encrypted text or in the best case no access is there of encrypted info.
NEXT In One Page – Spreadsheets vs Web Applications using Online Database