I feel like I’ve seen this discusses here in the past but if that exists I’m failing at search engines today. Next attempt was chopping session-specific chunks out of an actual browser client URL, which confused the browser client and either opens a blank page or redirects to the home page. Snooping through the browser client’s network traffic also didn’t turn up any obvious solutions.
I have some external BI and project management products which are being populated from Epicor data. I think the browser client has reached a state that I can responsibly promote it to my users. A nice way to do that would be if those products contained hyperlinks that directly opened something like a job, quote, or sales order to save them some clicks. Is this an actually hard thing, or have I overlooked something super obvious?
(https://<database>/<environment name>/Apps/Erp/Home/#/view/<MenuID CRMN9000>/Erp.UI.CustomerEntry?<channelid= some string db16affd-7748-4246-9509-b5ab98f22465>&company=<Company ID EPIC06>&site=<SiteID MfgSys>&pageId=Details&KeyFields.CustID=<CustID YOURCUSTOMER>&pageChanged=true)
I think the feature was called Deep Linking, which might turn up more results.
Yea, the channel ID is not needed, but for some reason, it was still a “required” field in the URL even if you didn’t have a link to another screen… FYI, it doesnt matter what you put into this… you can say “channelid = 0” or “channelid=123”, but whatever you do, if you have two or more channelids that are the same in two browser tabs, then they are linked.
I just tested this in Kinetic 2025.1, and I found that it is no longer a required element in the URL. Not sure which version this was eliminated as a required element, but you might try it in your versions… just eliminate the “channelid=blablabla” portion and see if the screen still works.
That’s even better news! I can confirm in 2024.2, deleting the channelid out of a URL dead-ends the page load to a blank screen. Sometimes providing a junk channelid does the same - part tracker doesn’t like it. Eliminating channelid as a required element surely removes a super annoying developer situation. As a downstream effect allowing users to easily produce a direct hyperlink can also be really impactful.
Of course I had to try linking two existing tabs by manually changing their channelid’s. Nope, doesn’t work that way. Which makes sense. A distinct channelid specific to each element in one tab that can be published eliminates a bunch of subscriber side context handling.
that worked. But hold on, what about Rule 
. I should know better. Just because something looks important, doesn’t mean it’s not a YAGNI artifact that snuck into release.