Lobby element navigational link - IAL datasource and Lobby Page Parameter

​@jtobin , ​@mlambert 

Generally, this is the best source of information on Lobby Navigation:

https://docs.ifs.com/techdocs/23r1/040_tailoring/250_lobby_configurations/080_navigation/#lobby_navigation_guideline

From what I see, you added a custom field to the Business Opportunity page, included it in your Lobby Data Source, and have it set as a Lobby Page Parameter to filter the Lobby Element.

It’s unclear from your posts what’s causing the navigation failure because of these two sentences.  Can you clarify why you’re saying that the BO doesn’t have the field to reference against, when you’ve shown that the field was added to the BO.  Are you saying there’s no value in the field or something else?

And I need to be able to pass the parameter BO_SALESMAN from the lobby over to the Business Opportunity screen.

I keep getting an error and I think it’s because the lobby uses BO_SALESMAN as the page parameter, but the Business Opportunity doesn’t have that field to reference against.

Hi ​@Tracy Norwillo ,

The IAL that we created has renamed the custom field from cf$_NAN_salesman to BO_SALESMAN. The Business Opportunity screen that we are trying to navigate to doesn’t have BO_salesman as a field, but has the original custom field cf$_NAN_salesman.

I was wondering if this was what was causing the navigational issues.

​@mlambert That should not cause an issue as long as you're using the correct field name in the Navigation url filter.

I set up a test case in an internal instance using a Query Designer source instead of an IAL.  I used an alias for Cf Salesman to simulate your IAL alias.

Here is the custom field:

Here is the Element with Navigation:

If I click on the “Matt” record, I go to the Matt BO.

If I click on the “jane” record, I go to the Jane BO.

One other thing to check is the Search Settings for the BO page.

I have mine set like this.  Check out the Navigation url I posted for the Tech Docs which shows you that you can pass these settings explicitly from the Lobby.

Hi ​@Tracy Norwillo , thanks for the write-up.

Unfortunately, I don’t see how your Lobby Page Parameter is involved.
This is my setup

Here is my element designer:

And this is my datasource designer:

This is the error that get with my navigation:

IFS Web Version: 23.1.8.20231206170215.0
Date: 2025-04-01T12:05:32.596Z

---------------------------------------------------------------------------

BusinessOpportunity/OpportunityOverviewPage (server error)
Malformed Request.
Error details: [{"code":"EXPRESSION_PROPERTY_NOT_IN_TYPE","message":"The property 'CF_Salesman', used in a query expression, is not defined in type 'IfsApp.BusinessOpportunityHandling.BusinessOpportunity'."}]

Request Id: a7b87d72-8920-4781-9633-7f20914b54e2

Url: https://ifs-prod-midtier.control-associates.com/main/ifsapplications/projection/v1/BusinessOpportunityHandling.svc/BusinessOpportunities?$filter=(%20CF_Salesman%20eq%20%27AKOSHY%27)&$orderby=DateEntered%20desc&$select=OpportunityTypeText,Objstate,SalesProcessConfirmed,ProcessId,OpportunityNo,Objgrants,ReasonNote,Note,ClosedStatus,LostTo,Description,WantedDeliveryDate,ExpirationDate,EstimatedSignDate,PriceEffectiveDate,DeliveryAddressId,DocumentAddressId,StartDate,Company,MainContactId,MainContactGuid,MainRepresentativeId,Status,CustomerId,NoteId,MainRevisionNo,Probability,ActualOppValue,CurrencyCode,StageId,DateEntered,OpportunityType,Cf_Nan_Coordinator,Cf_Nan_Salesman,EstOpportunityValue,MainContactName,BusinessType,SourceId,ClosureDate,ActualSignDate,MarketCode,RegionCode,DistrictCode,LeadId,DeliveryAddrEndCustomer,DocumentAddrEndCustomer,AdditionalDiscount,Cf_Nan_Customer_Po_No,luname,keyref&$expand=CompanyRef($select=Description,luname,keyref),CustomerRef($select=Name,Objgrants,luname,keyref),StageRef($select=Description,Objgrants,luname,keyref),BusinessOpportunity_Nan_Coordinator_Ref($select=Cf_DisplayText,luname,keyref),BusinessOpportunity_Nan_Salesman_Ref($select=Cf_DisplayText,luname,keyref),MainRepLovRef($select=Name,luname,keyref),WinReasonRef($select=ReasonDescription,Objgrants,luname,keyref),LostReasonRef($select=ReasonDescription,Objgrants,luname,keyref),SalesProcessRef($select=Description,Objgrants,luname,keyref),SalesMarketRef($select=Description,Objgrants,luname,keyref),SalesRegionRef($select=Description,Objgrants,luname,keyref),SalesDistrictRef($select=Description,Objgrants,luname,keyref),LeadRef($select=Description,Objgrants,luname,keyref),DeliveryAddrNoRef($select=Address,luname,keyref),DocumentAddrNoRef($select=Address,luname,keyref)&$skip=0&$top=25

---------------------------------------------------------------------------

​@mlambert Your Url in the error message seems to be indicating that the filter is being passed to the page. Can you check the target page to ensure that the custom field has been added there and that you have a Published Page Configuration containing the CF Salesman field there?