Backup obi202 configuration
jwcmb:
se1961,
Excel does all the work in setting up the filter for you.
First, I recommend that you select the "Incl. Default Values" and "Use Obi Version" options when creating the xml backup configuration file (see http://www.obihai.com/OBiAdminGuide.htm#_Toc333506084).
When you open the xml file in Excel, you will see a header row of column names, one of which is X_UD. You should also see drop-down arrow icons at the right border of each column name. When you click that drop-down, it shows you a summary listing of each unique value in the data rows, and there is a checkbox next to each value. For X_UD, there are just two unique values - "Y" (for this parameter is set at the Default) and "(Blanks)". Uncheck the "(Select All)" option, then check the "(Blanks)" option. The data will then be filtered for just those rows that have a setting different than the Default.
This works as described above for the Windows version of Excel I'm using (Excel 2013). I assume it works the same way for other versions, but haven't tested it on other versions.
Filtering is a very powerful and easy to use feature in Excel. If you find it useful, the Help screens or google searches will show many practical uses for it and tips for how to use it.
CoalMinerRetired:
Quote from: QBZappy on February 12, 2013, 08:55:57 pm
swl1961,
Quote from: se1961 on February 12, 2013, 05:22:21 pm
I have backed up my configuration by pasting screen shots into a word doc, so at least I can retrace my steps. :)
Well, if you're gonna do that, might as well make the backup and open the XML file using M$ excel. Open it in XML format and you get nice clean columns showing your config details.
A few months ago I tried an XL import. It never ever worked because some 'import errors.' Tried unsuccessfully to track them down, and eventually gave up.
After reading this I tried the import in Excel 2007 and it worked without any problem. I had previously been using Excel 2013. No idea why Excel 2013 saw errors, with no apparent work around.
se1961:
Wow. Great. Thank you so much. Not only is this device saving me money, it's making me a better and smarter person. ;D
jwcmb:
CoalMinerRetired,
It looks like we both replied at the same time. I'm glad to hear that Excel sets up the filter on importing the xml in the 2007 version, as it does in 2013. Maybe all the versions will do that???
jwcmb:
CoalMinerRetired,
I'm surprised that it didn't work when you tried the Excel import with version 2013. I'm curious as to whether the "Use Obi Version" option might be the reason. I chose that option. Did you use that option? Perhaps it might make a difference in how Excel is able to transform the xml??
When I do the import into Excel 2013, I first get a message saying "Please select how you would like to open this file:". I went with the default choice: "As an XML Table".
Then I got a message saying: "The specified XML source does not refer to a schema. Excel with create a schema based on the XML source data." After clicking OK, the data got imported ok.
Navigation
[0] Message Index
[#] Next page
[*] Previous page