In terms of the AR API I do not know what the difference is but from experience using values directly from table fields sometimes doesn't work as expected. Maybe the row is being unselected (unnoticeably) right be for the Commit action?
I agree it *should* work. Often times doing a Set Fields from a Table Field before using in workflow is required when doing an AL/Filter loop on a Table Field however it is one thing to try with your Commit/Close Window to rule out these kinds of issues. Beyond that I am assuming the Table Field is visible, you can see the data in the TF and that the row is selected before the Commit/Close Window? That should rule out most permissions issues. If the TF is not visible then there a few things we can explore there. Does it happen for everybody? One user or set of users? Is it only in IE? Can you pound on this functionality in Firefox a little to verify it is a browser-specific issue? Jason Hi Jason, actually I just maybe wrote it wrongly that Globa Field. It's a normal field on the calling form which should be filled On Close of the called form. The Idea of stroring the value from table to a field before is nice but at the end, where is the difference. On Close I mapped the value chosen from the table. In that way I will just map the value from a filed. I don't think there will be some difference. however, problem is this is happening either in normal mode (not private) of the explorer. but it's sudden and I cannot replicate that so easily :( however, thanks a lot for tip :) Marek _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
