geoffdude

I'm trying to figure out a way to change any character submitted to data table field, that's not 0-9 or A-Z/a-z to something else, using formula logic. I'm new to formulas, and this is what I'm playing with .. but it's not working as desired. It only runs the first "When" statement and ignores the others. CASE When Charindex ('''',[@field:promo], 0) <> 0 Then Replace([@field:promo], '''','') When Charindex ('é',[@field:promo], 0) <> 0 Then Replace([@field:promo], 'é','e') When Charindex ('ü',[@field:promo], 0) <> 0 Then Replace([@field:promo], 'ü','u') ELSE ( [@field:promo]) END Any tips, or ideas would be greatly appreciated. Thx

Still a bit confusing to me .. however, how would the product "fail" lining inspection? What process in the flow validates/checks for a "pass" or "fail"?

If you want to hide the info on result page of some kind, give your DIV an ID (use "box1") then try this: <script type="text/javascript"> document.addEventListener('DataPageReady', window.onload = function(){ var x = document.getElementsByName("InsertRecordZip3")[0].value; if (x == "") { document.getElementById("box1").style.display = 'none'; alert("Nothing entered - box hidden"); } else { document.getElementById("box1").style.display = 'block'; alert("Word entered - box not hidden"); } }); </script> <!-- add a style tag, with "box1" display set to 'block', then update your code for the DIV as below --> <style> #box1 {display:block}</style> <div id="box1" style="background:#eee;border:1px solid #ccc;padding:5px 10px;">Address:<br /> [@field:Address3]<br /> [@field:City3], [@field:State3]<br /> [@field:Country3], [@field:Zip3]</div>

Can you provide a wire-frame of the flow that way we can see what's supposed to happen. Like: Product = GARMENT X Serial Number = 123456 Emp Id = TestID-00001 Station = Choices (Station A, Station B, etc) Then create the wire-frame for us to look at ... like this example below, except show your form fields w/names and what should happen with it's use (It will help us to figure out the flow/logic.)

Excellent .. happy to help.

My first thought is you CSS in causing errors. The form CSS may be the issue .. but it's hard to determine without seeing the form live. Some things to try on the code you provided are as follows: <style> .ui-resizable-helper { border: 1px dotted gray; } ul#menu .activeMenu { background: #bb3033; } ul#menu { width: 100%; background: #21618C; font-size: 10px; font-family: "Arial", sans-serif; font-weight: bold; list-style-type: none; margin: 0; padding: 0; text-align: center; } ul#menu li { display: block; display: inline-block; margin: 4px 0 0 0; padding: 5px 15px 5px 15px; cursor:pointer;} ul#menu li a {color: #fff; text-decoration: none; display: block; line-height: 200%; } ul#menu li a:hover { color: #333; } /* FIX(1) move li styles here */ li { font-size: 11px !important; font-weight: bold !important; } /* FIX(2) get rid of padding, border, make width 100%, get rid of display block and position too, make background grey for testing only */ .content{width: 100%; height:1024px; background: #e5e5e5; padding: 0px; border:0px solid #21618C; overflow:hidden;} /* FIX(3) get rid of padding, make width 50% (iFrame width), make background blue (iFrame background color) for testing only */ .ChannelView{ width:50%; height:100%; margin-bottom:100%; background:#aae2ee;} /* FIX(4) disable this media query as it does nothing for this page @media (max-width: 1024) { .content { width: 96.6%; background: #ff0000 !important; } } */ </style> Let see what this style code change does, then go from there.

You may need to create a copy of the form, then remove all the JS associated with that form and start testing by introducing portions of the script back into the test-form. You can also create a 3rd form copy to just focus on the fields that use the scripts, and run tests on these new forms to see when the error occurs. - It's a pain, but part of the developer process at times. Hunt and peck so to speak... without messing up your OG form.

What was your code for the link opening a new window? Were you using <a href="somecaspioURL" target="_blank"> LINK HERE</a>? The code target="_blank" works for me.

Also .. the referrer field will ONLY capture the domain address if the previous page links to your page. It must be a REFERRING domain.. so an active page on a live domain will work .. testing from your 'puter on a local page (from your 'puter) will not.

You need to pass the "Virtual7" value as a "parameter" in your form's advance setting for that field- such as: On exit: Pass field value as parameter: [@Virtual7] Then on your report page have that virtual field set as display only, but also have it set to receive the parameter: Receive value or parameter: External Parameters = [@Virtual7]

Do you have the Virtual7 form field set as: Form element: Text Field If you have Virtual7 set as display only like: Form element: Display Only it won't work.

Where, and how, are you placing the code? * I tried your code and it works for me.

Maybe create a wire-frame for us to look at ... like this example below. It may help to figure out the flow/logic. Sample wire-frame:

I'm on 20.3 .. strange huh? Update: I had to clear my cache to see the new version changes. It's all good now.

Is "Loops" even available for tasks anymore? I don't see it.