List of Virtual fields in SearchEngine

Hi Dennis,

Archive provider columns...

Consider, instead of using SearchEngine, using ArchiveProviders directly...

NSArchiveRestrictionInfo[] restrictions;
NSArchiveRestrictionInfo res1;
res1.SetName("fullName");
res1.SetOperator("contains");
res1.SetValues(String("Dennis Aagaard Mortensgaard").split(","));
restrictions.pushBack(res1);

NSArchiveOrderByInfo[] order;
 
String[] entities = String("person").split(",");

Integer pageSize = 250;

NSArchiveAgent archiveAgent;
NSArchiveListItem[] rows = archiveAgent.GetArchiveListByColumns("SimplePerson", String("personId,fullName,email/emailAddress").split(","), order, restrictions, entities, 0, pageSize);

foreach (NSArchiveListItem row in rows) {
  Map rowData = row.GetColumnData();
  String person_personId = rowData.get("personId");
  String person_fullName = rowData.get("fullName");
  String person_emailAddress = rowData.get("email/emailAddress");
  
  printLine(person_personId + ": " + person_fullName + " => " + person_emailAddress);
} 

Best regards.

Hello Dennis, 

I'm not sure if it completely answers your question (and you already have gotten very nice feedback from both Tony and Simen), but you could also go through the API to get available fields/columns. 
Take a look at our Custom objects search documentation.

To build on Tonys example for SimplePerson:

POST {{api_url}}/v1/Agents/Archive/GetAvailableColumns?$select=name HTTP/1.1
Authorization: Bearer {{access_token}}
Accept: application/json; charset=utf-8
Content-Type: application/json

{
  "ProviderName": "SimplePerson",
  "Columns": ""
}

This should return a good idea of what columns you have available for that Provider, and would make it easy to work with `GetArchiveListByColumns`

//Eivind

Virtual fields declared with in the CDD/database model:

But like Tony said, there is a reason these are set using 'legacy' flags in the database model. You should be using the default archive provider if possible, and if they dont fit your needs, use the Dynamic archive provider since then you have the full advantage of the dot syntax (CRMScript searchgine doesnt support all of it, like the [ ] notation to force join tables).

Thank you :)