After giving it a little thought, I realized that the Replace(x,y,z) function does the trick just fine, where x is the list of 'true's and 'false's, y is either 'True' or 'False', and z is either '1' or '0'.
I'm sure other users were a little quicker to get there than I was. Best, James On Nov 27, 2:25 pm, James Lucas <[EMAIL PROTECTED]> wrote: > I'm under the impression that these conversions are not yet > integrated. Are there any known workarounds? > > Thanks, > > James > > On Oct 14, 8:25 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > Just added these conversions again, it will be available in the next > > version. > > > BooleantoNumber (False becomes 0 (zero), True becomes 1 (one)) > > > NumbertoBoolean (Zero becomes false, Non-zero becomes true) > > > -- > > David Rutten > > Robert McNeel & Associates > > > On Oct 14, 4:12 pm, David Rutten <[EMAIL PROTECTED]> wrote: > > > > Lisa, > > > > there's been another report on this. I'm looking into it now. > > > > -- > > > David Rutten > > > Robert McNeel & Associates > > > > On Oct 14, 12:14 pm, Lk <[EMAIL PROTECTED]> wrote: > > > > > I haven't read through all the emails about the new version, so I may > > > > have missed this, but did the way that functions outputbooleandata > > > > change? I have been using the results from functions like ">" and "<" > > > > to plug into scalar operators, and now I'm getting errors that there > > > > aren't values, like the trues and falses aren't recognized as 1s and > > > > 0s, anyone know anything about this or have an idea of how I could do > > > > this as simply with the new version? > > > > > Thanks!
