Hi, do I miss something here? Opening a project stored in a previous version of Phoenix variable’s units are correctly displayed (in brackets). However, if I setup a new worksheet units are displayed in red - regardless whether I enter the unit directly in the “Unit” field or use the “Unit Builder”. Example “h” for time: Warning “The Units specified (h) may be an invalid unit. Do you wish to continue?”. If I insist, units are given in curly brackets. They are carried over through the analyses and lead to disgusting headers, e.g., AUMC ({{h}}{h}{ng/mL}})…
Sorry Helmut, you found something that slipped into PHX 1.3 and we have prepared a patch and the notification is just being finalised for signing. You can download the patch now and I can only extend our apologies. Simon Valid units not recognized with some Regional Options that are non-US (QC 11920/CRM 136733): On machines where non-US Regional Options are used, this problem can be observed when importing a dataset with units from any source (PMO, CSV, DAT, XLS, *.PHXPROJ, etc.), or when specifying units on an already imported dataset. The worksheet headers of the data will get curly braces “{ }” around valid units, indicating that the units are invalid. Since these units are marked as invalid, unit conversions and relabeling cannot be done. The problem occurs in different locales where NaN (i.e., “Not a Number”, shown as a blank cell in a worksheet) is represented as more than one word. For example, in French NaN is represented by “Non Numerique”. One workaround is to change the Regional Options to English (United States). However, if the user wishes to use Regional Options other than English (United States), Pharsight is providing a patch in conjunction with this Product Notification to resolve this problem. To correct this issue, a new file “unitconverter.exe” can be downloaded using the link below: ftp://support_ftp:pt9JTmD9GdXQLtCgPkvL@ftp.certara.com/support/desktop/Phoenix/unitconverter.zip [file name=PHXnot12.pdf size=67004] /extranet/media/kunena/attachments/legacy/files/PHXnot12.pdf[/file]PHXnot12.pdf (65.4 KB)PHXnot12.pdf (65.4 KB)
Hi Simon, THX, works even on projects saved with “invalid units”. Needs re-execution of some objects. Shall I charge Pharsight one day searching for an error I assumed to have made myself? 
I’m wondering why I haven’t seen this bug in the beta version…