When you specify main tables to include in an offline publication, all the related detail tables, lookup tables, views, and other database objects are included automatically in your offline publication. The only time you must modify the database objects list is when you want to remove a main table from your publication. Removing a main table does not drop automatically related tables. In fact, it is possible to re-create your publication with broken references.
For example, the Issue Tracking solution might use a date column to calculate and display the age of an issue. If you exclude the table with that date column from the offline publication, your publication will not run properly.
To avoid problems with broken references, when you remove a main table and attempt to re-create a publication, you receive a warning that lists the related objects that have broken references.
If you remove a database object, test your solution to make sure the offline publication performs properly without it.
To include or exclude other database objects from a publication
It is recommended you test your solution to verify that all objects the solution requires to work properly offline are included in the publication.