I am using @URLQueryString to pass a link from form A in Db A to a new form in a second Db. The link resides in a computed field with @URLQueryString(“link”). This works fine… but am wondering about web domain change. form A has a hidden field that computes the link based on @WebDbName + DoCID. e.g. https://test.abc.com/sample.nsf/0/docID. When the domain changes to test.123.com, the computed links in existing forms will be incorrect. Any ideas? Will we have to create an agent that replaces test.abc.com -w- test.123.com?
Subject: @WebDbName & Computed Field (DOmain Change)
I think you mean the computed links will be incorrect on the DOCUMENTS, not the forms - forms don’t really save computed field values. Why not use computed for display fields instead - that way, the domain value won’t actually be saved on the documents, and therefore will recompute each time a document is loaded.
Subject: @WebDbName & Computed Field (Domain Change)
Thanks Esther… you are 100%. I meant documents vs. forms. Sounds like I should be passing the docID only then field formula (computed for display…) should be @WebDbName + “/0/” + whatever the URLQuery is. Actually… this would not work because @WebDbName would return the current Db vs. the original DB as required. Guess I could trim and replace with old Db name. Hmmm… is there some way to call just the domain name? e.g. http://www.test.com then add the rest in the formula?
Subject: RE: @WebDbName & Computed Field (Domain Change)
Try @GetHTTPHeader(“Host”)