Try using ?export=1&enc=UTF-8&xf=xls
for the query string.
e.g. /00Oi0000002vZ5W?export=1&enc=UTF-8&xf=xls
You might want to change &enc=UTF-8
with &enc=ISO-8859-1
depending on the file encoding you want.
You can also get a CSV by changing the xf parameter to &xf=csv
.
In a custom button or link using window.open will prevent the current browser window being redirected.
window.open('/00Oi0000002vZ5W?export=1&enc=UTF-8&xf=xls');
This is a many to many object model which will utilize a 'junction object'. Employing a pair of lookups defined on the junction object with a structure that looks like this:
Author (Contact)
<-- lookup Paper_Author__c
lookup --> Paper__c
This model supports an Author
on many Papers
as well as a Paper
having many Authors
. It also will give you the ability to display the related lists per Author
and per Paper
which you're interested in by showing the Paper_Author__c
list in each case.
You state that it is 'up to 10' Authors on a paper and I would highly recommend against you defining the object model with Author 1, Author 2, Author 3 etc. This is going to be a painful thing to overcome in the future when the '10 author' model doesn't work any longer.
The many to many model using the junction object, is the proper implementation of this concept, allows for an 'unlimited' number of Authors
on a Paper
and is 100% future-proof.
Additionally, the Author 1, Author 2, Author 3 lookup field model will not allow you to display a related list of Papers an Author has contributed to.
The junction object is the correct approach in all cases.
Best Answer
You can use Object Metadata Snapshot tool from Appexchange to export object details to excel.
or
Etherios - EasyDescribe