-
Craig,
Has the fix resolved the issue?
could you please post the web.config change
-
Carol,
here is a direction you should be going in:
in your AI job for External Data Source use "SQL statement"- Content Database Connection, and the following statement (make adjustments if your FullName column is in format other than "FirstName LastName":
select FullName, substring(FullName,1, charindex(' ',FullName,1)-1) AS fname, substring(FullName,charindex(' ',FullName,1)+1,100) AS lname from filecabinetname
do a match on FulName=external Field FullName and assign your two new columns with values of fname and lname
Hope this helps.
-
David,
have you checked the new option available in Store dialogs for a field Predefined Entry "Automatic Numbering". If you assign the field you referring to in your question to this type of Predefined Entry in all dialogs that store particular doctypes, you will accomplish what you need w/o any SQL scripts.
-
-
Shimon,
if a stamp that configured as a signature stamp has been applied to a document, this is an expected behavior: no more annotations can be applied. If you want to be able to apply annotations after stamps, then all of the stamps must be configured as non-signature.
-
Has anyone seen this issue when concurrent licenses (converted to such from post 6.11 named licenses by administrator) revert themselves back to named licenses on server restart?
One of my customers claims it's happened twice to them, but I could not replicate by trying multiple services restarts and reboots.
-
Phil,
yes with field visible with custom value and Read-Only it works as expected, but that is an extra field on users dialog that could be done without.
-
Phil,
this is how it works, but should that be the way it works? If a custom value hidden field works in a store dialog should not it also woprk for select list filtering?
Do you think it would be a good candidate for a feature request, or not a chance?
-
If I have a multi-column select list (ColA and ColB) and a store dialog (or an index dialog) where I associate a field1 with ColA filtered by Filed2=ColB, and configure Field2 be a custom value - the dropdown list for Field1 appears as expected: it filters values from select list based on Field2 predefined value.
But if I want to hide Field2 from the dialog - then the filtering stops working.
This is very strange as using a store dialog with custom value hidden field works as expected. Just the problem with filtering of select list.
-
Steve,
use the following syntax (OR must be in capitals).
Value1 OR Value2 OR Value3