@HamidBee
Just to add a bit more detail around this question:
1 - The common data model provides a simple way for novice app builders to start building apps that are based on the standard tables. For a complete beginner, it's easier to re-use a standard table instead of creating one from scratch.
More importantly, beginners without any database experience can often create tables that are poorly designed. That is, tables with repeating data and tables without properly defined lookup fields and relationships. The common data model provides a means to overcome this difficulty.
2 - The common data model encourages the centralisation of data. It can help avoid the situation where multiple app builders create separate 'customer' tables, and avoid the future requirement of having to consolidate data do you want to share that's now ended up in separate tables.
3 - The schema of the common data model attempts to closely align with the schema of Microsoft competitor products like SAP or Salesforce. For organisations that use other products, the task of synchronising or importing/exporting data is less challenging because data mappings between products should be more aligned.
>> Let's say I have a table that I would like to populate into this table but I only need say 10 of those columns. How would I go about populating them. Would I have to only show those 10 columns and then copy and paste them from say Excel straight into the table?. Would this be the common way of doing it?.
In answer to your data population question, you would typically create a dataflow that carries out the import process and you would only select only the 10 columns that you want to match.