Sage 100

Hi everyone,

What is the proper way to copy BIE views from one installation to another. I know during an upgrade they will transfer just fine but we have some BIE views created by one of our consultants that we would like to share with the rest of the team for demo and training purposes. Manually copying the files from one installation to another doesn't seem to work as those views then don't show up in the drop down list. And the Custom Office export/import task will only work if they are on the same version. I know we can recreate them but I would hope there is a better way than that. Is there a way to transfer these that I am missing?

Thanks!

------------------------------
Jesse Braun
Vrakas/Blum Computer Consulting, Inc.
------------------------------

Jesse,

I encountered this issue a few days ago on a Premium Version 2019 install.  For public views, you can use the Custom Office export utility on the Utilities menu, then use the import utility in the new installation.  This is tedious, however, because you can only copy one setting per view, so if have multiple settings for the same view, it entails running the utility multiple times and creating multiple export files them importing each file one at a time.

I used the above process for Private views as well, and the import said they were successful, but the views weren't there.  So I copied the files from the \MAS90\BIExplorer\Views folder to the new installation and they appeared.  This method may work for the Public views as well - had I known it would be that easy I would have tried this first.

Let us know the result - I'll be interested to know if the file copy works for the Public views!

------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
------------------------------

Public views are saved on the server in MAS90\BIExplorer\Views\[View Name]
Private views are saved on the server in the MAS90\BIExplorer\Views\[View Name]\Private\[User Logon]
As long as you don't have any view naming conflicts between the source and the destination, you should be able to selectively copy the folders at the view name level.  I don't know how likely it is that Sage would change the view name between versions so that is the only reason I would caution against copying the entire BIExplorer folder.  You would also would to make sure that the source view isn't named the same as a view in the destination that is configured differently.  This is more likely if using very vague or default view names like "Standard" or "Default".  I can't find any evidence that the view names are stored in a table, it appears as though BIE simply scans the BIExplorer\[View Name] folder for the current view and loads the Setting drop box based on what it finds in the folder and its sub folders for private views.

Also, if you have multiple "workstations" installed on a PC, finding the exact BIExplorer folder may be tricky, it appears to use the MAS90 path on the server from the last workstation to be installed, even if you have multiple versions installed.  As far as I can tell, this is because the registry entry is not separated by version, instead it is stored in [HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90] in the ViewsPath string value.  I also found an instance of those keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\BIE Explorer\Products\MAS90]

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Could this method be used to get around version copies if they are different?  like 2019 to 2020?

------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 05-21-2021 13:55
From: David Speck II
Subject: Copy BIE views to new installations

Public views are saved on the server in MAS90\BIExplorer\Views\[View Name]
Private views are saved on the server in the MAS90\BIExplorer\Views\[View Name]\Private\[User Logon]
As long as you don't have any view naming conflicts between the source and the destination, you should be able to selectively copy the folders at the view name level.  I don't know how likely it is that Sage would change the view name between versions so that is the only reason I would caution against copying the entire BIExplorer folder.  You would also would to make sure that the source view isn't named the same as a view in the destination that is configured differently.  This is more likely if using very vague or default view names like "Standard" or "Default".  I can't find any evidence that the view names are stored in a table, it appears as though BIE simply scans the BIExplorer\[View Name] folder for the current view and loads the Setting drop box based on what it finds in the folder and its sub folders for private views.

Also, if you have multiple "workstations" installed on a PC, finding the exact BIExplorer folder may be tricky, it appears to use the MAS90 path on the server from the last workstation to be installed, even if you have multiple versions installed.  As far as I can tell, this is because the registry entry is not separated by version, instead it is stored in [HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90] in the ViewsPath string value.  I also found an instance of those keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\BIE Explorer\Products\MAS90]

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

I'm not exactly sure what you mean Alan but I haven't seen anything like a version in the .ev files so the only reason i suspect there might be an issue is if a table and/or field name changed between versions.

------------------------------
David Speck II
Tennessee Software Solutions
------------------------------

Original Message:
Sent: 05-24-2021 15:44
From: alan niergarth
Subject: Copy BIE views to new installations

Could this method be used to get around version copies if they are different?  like 2019 to 2020?

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 05-21-2021 13:55
From: David Speck II
Subject: Copy BIE views to new installations

Public views are saved on the server in MAS90\BIExplorer\Views\[View Name]
Private views are saved on the server in the MAS90\BIExplorer\Views\[View Name]\Private\[User Logon]
As long as you don't have any view naming conflicts between the source and the destination, you should be able to selectively copy the folders at the view name level.  I don't know how likely it is that Sage would change the view name between versions so that is the only reason I would caution against copying the entire BIExplorer folder.  You would also would to make sure that the source view isn't named the same as a view in the destination that is configured differently.  This is more likely if using very vague or default view names like "Standard" or "Default".  I can't find any evidence that the view names are stored in a table, it appears as though BIE simply scans the BIExplorer\[View Name] folder for the current view and loads the Setting drop box based on what it finds in the folder and its sub folders for private views.

Also, if you have multiple "workstations" installed on a PC, finding the exact BIExplorer folder may be tricky, it appears to use the MAS90 path on the server from the last workstation to be installed, even if you have multiple versions installed.  As far as I can tell, this is because the registry entry is not separated by version, instead it is stored in [HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90] in the ViewsPath string value.  I also found an instance of those keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\BIE Explorer\Products\MAS90]

------------------------------
David Speck II
Tennessee Software Solutions

Jesse and Alan - The methods for moving BIE views mentioned by Susan and David to copy the appropriate folders under \BIExplorer\Views\ is the way to go, not the Customizer Import Wizard. However I would definitely use it for importing UDFs, UDTs, Advanced Field Settings, and User Defined (event) scripts and below is how you can override the restriction of same version enforcement:

Official Warning and Disclaimer: Do this at your own risk and make a backup before proceeding.

Realistic Warning: Do NOT override the Import Wizard for importing screen customizations ("customized tasks" as it's called). Also do not use for "Additional files" for an entirely different reason. Also do not do this late at night while your brain is circling the drain.

Edit the SOTA.INI file in the [Config] section and add this new line. Then restart the Launcher.
DevelopmentSystem=1

Note: For Advanced/Premium the change is made to the SOTA.INI in the location where you ran Workstation Setup
e.g. C:\Program Files\Sage\Sage 100 Workstation\Mas90\Launcher\
For Standard, it's the SOTA.INI on the server (also used if you start up Adv/Prem in Mas90 mode).

** Now when you point it to the M4X file it will let you proceed with the same warning. A Yes/No pop-up instead of an OK box.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------

Original Message:
Sent: 05-24-2021 15:44
From: alan niergarth
Subject: Copy BIE views to new installations

Could this method be used to get around version copies if they are different?  like 2019 to 2020?

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 05-21-2021 13:55
From: David Speck II
Subject: Copy BIE views to new installations

Public views are saved on the server in MAS90\BIExplorer\Views\[View Name]
Private views are saved on the server in the MAS90\BIExplorer\Views\[View Name]\Private\[User Logon]
As long as you don't have any view naming conflicts between the source and the destination, you should be able to selectively copy the folders at the view name level.  I don't know how likely it is that Sage would change the view name between versions so that is the only reason I would caution against copying the entire BIExplorer folder.  You would also would to make sure that the source view isn't named the same as a view in the destination that is configured differently.  This is more likely if using very vague or default view names like "Standard" or "Default".  I can't find any evidence that the view names are stored in a table, it appears as though BIE simply scans the BIExplorer\[View Name] folder for the current view and loads the Setting drop box based on what it finds in the folder and its sub folders for private views.

Also, if you have multiple "workstations" installed on a PC, finding the exact BIExplorer folder may be tricky, it appears to use the MAS90 path on the server from the last workstation to be installed, even if you have multiple versions installed.  As far as I can tell, this is because the registry entry is not separated by version, instead it is stored in [HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90] in the ViewsPath string value.  I also found an instance of those keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\BIE Explorer\Products\MAS90]

------------------------------
David Speck II
Tennessee Software Solutions

thank you @Alnoor Cassim and @David Speck II for your input.  Overriding the limitation of not being able to export UDF's from one version into a .M4X file then importing into a different version was my primary concern. This pops up fairly regularly just within use of my internal demo systems. Anxious to give it a try.  I could see that care would be needed for file structure changes.   ​​​

------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 05-24-2021 19:19
From: Alnoor Cassim
Subject: Copy BIE views to new installations

Jesse and Alan - The methods for moving BIE views mentioned by Susan and David to copy the appropriate folders under \BIExplorer\Views\ is the way to go, not the Customizer Import Wizard. However I would definitely use it for importing UDFs, UDTs, Advanced Field Settings, and User Defined (event) scripts and below is how you can override the restriction of same version enforcement:

Official Warning and Disclaimer: Do this at your own risk and make a backup before proceeding.

Realistic Warning: Do NOT override the Import Wizard for importing screen customizations ("customized tasks" as it's called). Also do not use for "Additional files" for an entirely different reason. Also do not do this late at night while your brain is circling the drain.

Edit the SOTA.INI file in the [Config] section and add this new line. Then restart the Launcher.
DevelopmentSystem=1

Note: For Advanced/Premium the change is made to the SOTA.INI in the location where you ran Workstation Setup
e.g. C:\Program Files\Sage\Sage 100 Workstation\Mas90\Launcher\
For Standard, it's the SOTA.INI on the server (also used if you start up Adv/Prem in Mas90 mode).

** Now when you point it to the M4X file it will let you proceed with the same warning. A Yes/No pop-up instead of an OK box.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------


Original Message:
Sent: 05-24-2021 15:44
From: alan niergarth
Subject: Copy BIE views to new installations

Could this method be used to get around version copies if they are different?  like 2019 to 2020?

------------------------------
alan niergarth
Velosio LLC


Original Message:
Sent: 05-21-2021 13:55
From: David Speck II
Subject: Copy BIE views to new installations

Public views are saved on the server in MAS90\BIExplorer\Views\[View Name]
Private views are saved on the server in the MAS90\BIExplorer\Views\[View Name]\Private\[User Logon]
As long as you don't have any view naming conflicts between the source and the destination, you should be able to selectively copy the folders at the view name level.  I don't know how likely it is that Sage would change the view name between versions so that is the only reason I would caution against copying the entire BIExplorer folder.  You would also would to make sure that the source view isn't named the same as a view in the destination that is configured differently.  This is more likely if using very vague or default view names like "Standard" or "Default".  I can't find any evidence that the view names are stored in a table, it appears as though BIE simply scans the BIExplorer\[View Name] folder for the current view and loads the Setting drop box based on what it finds in the folder and its sub folders for private views.

Also, if you have multiple "workstations" installed on a PC, finding the exact BIExplorer folder may be tricky, it appears to use the MAS90 path on the server from the last workstation to be installed, even if you have multiple versions installed.  As far as I can tell, this is because the registry entry is not separated by version, instead it is stored in [HKEY_CURRENT_USER\Software\Sage Software\BIE Explorer\Products\MAS90] in the ViewsPath string value.  I also found an instance of those keys in [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sage Software\BIE Explorer\Products\MAS90]

------------------------------
David Speck II
Tennessee Software Solutions