Administration, Core Financials, and Project Accounting

[TRoop]

Folks,

I am hoping someone can answer this and it is something I am just plainly missing. On some of our Mas 500 standard reports (an example would be the Pack List Form), there are some formula fields that contain some variables that appear to some kind of report variables. I am trying to figure out where these are stored and am not having much luck.

The formula call will be something like FreeFormText("kSOShipTo")

Can someone tell me if those are local variables or are they parameters that are being read from a DB call?? 

[Ralph]

Tim, I don't know what the FreeFormText function does, but in case you hadn't already noticed, it is a Sage-provided User Function Library (UFL) function that is contained in u2lsota.dll.  You can see this in the Formula Editor window by expanding Functions --> Additional Functions --> sota (u2lsota.dll).

Looking at sozrg003 for example, it appears that FreeFormText is mostly used in labels.  This is a just a guess, but maybe it's used to alter the appearance of the label based on certain settings in System Manager --> Maintenance --> Maintain Report Format.

That's probably not much help, but I wanted to make sure you had noticed that FreeFormText is a Sage-provided function.

[TRoop]

Thanks Ralph...

This did get me a step closer to the end result as I overlooked this in the formula list. However, I believe these values are constants that maybe are being passed in from dll so the actual values aren't being displayed until the report data is returned.

if this is the case....  bummer!!

I guess as long as they are truly constants and the parameter doesn't have multiple values potentially being passed, I should be ok to edit the formula and add in what I need to here.

[TRoop]

So far I have been able to modify the formula to display the text displayed and it has produced the correct results. It would still be nice to have an accessible list of all those constant values that are to be displayed on a form though (without having to print one to find out)...

[trodman · Accepted solution]

Tim,

Try this.  I think the idea of using those variables is that, theoretically, you could store multiple languages in the tsmLocalString table and never have to modify the Crystal reports.

SELECT tsmString.ConstantName,tsmLocalString.LocalText
FROM tsmLocalString
	JOIN tsmString ON tsmLocalString.StringNo=tsmString.StringNo
WHERE tsmString.ConstantName='kSOShipTo'

[TRoop]

Perfect!!  Thanks Tim...