Key Values in URLs

1 minute read time.

If you do any customization. Then very quickly you start to build hyperlinks that need to bring you directly into the correct context.

Consider this partial URL from the Summary tab of the Company context.

... &act=200 &key0=1 &key1=28 &key2=30...

The keys can be read to understand

Key0 = current entity in context
Key1 = company unique id
Key2 = person unique id

So assuming we are working with the standard demo data then we are currently looking at Gatecom and Simon Yaltoy.

But what are the other keys that are used.

Here then is the list.

DOMINANTKEY=0;
Companyid=1;
Personid=2;
Addressid=3;
Userid=4;
ChannelId=5;
CommunicationId=6;
OpportunityId=7;
CaseId=8;
NoteId=9;
TeamId=10;
UserAdminId=11;
ChannelAdminId=12;
LockId=13;
TranslationId=14;
LibraryId=15;
ProductId=16;
CaseProgressId=17;
OpportunityProgressId=18;
CompanySearchKey=19;
PersonSearchKey=20;
OpportunitySearchKey=21;
CaseSearchKey=22;
CommSearchKey=23;
TargetListList=24;
TargetListId=25;
OpportunityItemId=26;
WorkflowId=27;
WorkflowActionId=28;
CustomDatabase=29;
CustomTable=30;
VisitorId=31;
UserPrefId=32;
CampaignId=33;
WaveId=34;
WaveItemId=35;
RecurrenceId=36;
ForeignTableId=37;
DataUploadId=38;
MatchRulesId=39;
CurrencyAdminId=40;
ReportId=41;
ComponentId=42;
ComponentScriptId=43;
LeadId=44;
LeadSearchKey=45;
WorkflowStateId=46;
MainWorkflowId=47;
HelpLinkId=48;
TransitionId=49;
InstanceId=50;
UserDeviceId=51;
Article=52;
Subscription=53;
TerritoryId=54;
LeadProgressId=55;
LeadOppoMapId=56;
RuleManagement=57;
CustomEntity=58;
TerritoryProfileId=59;
FilterProfileId=60;
GenericPage=61;
ReportSearchID=62;
CallID=63;
ForecastID=64;
CustomViewID=65;
BusinessCalendarId=66;
HolidaySetId=67;
SolutionsId=68;
SolutionSearchKey=69;
SolutionProgressId=70;
ForecastHistoryID=73;
SLAId=75;

Anonymous