i am using obiee 11g and I want to extract some documentation out of the catalog manager. I explain. I have some analyse with some views I added like for example a title and a static text. I renamed those views to documentation. Now I want to extract for each analyse those two views. I thought I could do that with the catalog manager and the tool>extract report like I saw some examples here.
The problem is that I don't find how I can extract the view or compound layout with the catalog manager.
You can archive and unarchive the analysses and dashboards etc..
And unarchive to anywhere or any server you have the same Model ...
Go to catalog, select your analysis, archive , and unarchive ll be at down left corner:
Related
When trying to create a report for the catalog objects in OBIEE (12c) through the Catalog Manager tool, it is supposed to give me the type of object I want to create the report for. But for me that selection is not coming at all. In some forums it is mentioned that run the catalog manager not through the shortcut but through the runcat.cmd file in Oracle_Home/bi/bitools/bin directory, but even that didn't help.Here's what I am seeing:
And here's what I am supposed to see:
Any insights would be appreciated.Thanks
I've been trying to transfer the entire catalog from one Magento server to another and I've been experiencing some significant problems.
I can get most of the catalog data across, but I always end up missing something like product swatches, product categories or a product's custom options. To get these across I then end up building my own scripts that queries Magento, writes the data to a CSV file of my own design, and then write another script that will add this data to the other server.
Ive been asking the other developers in house, and apparently this is how they do every migration. They spend ages building lots of custom scripts just to transfer the catalog across, and apparently the different Magento sites are so different they have to build entirely new scripts when they transfer the next site.
Is this a common experience for everybody?
I feel like there must be a better way. Does anybody know of a better way to transfer the entire catalog (not just the products, but everything) to another server? Can we not just copy across the entire SQL Database?
You can export the products using Magento export wizard by going into System -> import/export ->export
Then from export settings select Entity type Products and Export File Format as CSV
After getting the CSV file you can import the whole catalog using the Magento same wizard or You can use data flow.
The other option around to import bigger catalogs in Magento is to Use Magmi.
http://wiki.magmi.org/index.php?title=Magmi_Wiki
I hope this will help
There are many ways you can migrate your magento store from one server to another.
If you want to transfer complete magento site, then you should try with database import/export. Its easy and fast process. You can follow Site Ground tutorial for this
If you want to transfer only data such as product, catalog, customers, orders etc, then you can try magmi importer its easy and fast for importing data. Also you can try magento data flow profiles as well.
I am adding regions of a country to the database in Magento so when a user selects their country a relevant list of regions will be available in a drop down menu. To do this I believe I need to add information to directory_country_region and directory_country_region_name.
The tutorial I've been looking at states that I should add them directly to the database using sql, however I remember reading that you should not place information directly into the database using raw sql when working with Magento.
My questions are:
1- to keep in line with best practices do I need to use some magento functions to add the required information to my database or can they be dropped in using raw sql?
2- if I need to use some Magento functions how do I work out which I need to use (I have heard off and noticed the lack of documentation) or is there some online reference, even if it is limited?
3- if I am not to use a sql query why is it considered bad practice to do so in Magento?
Hello, if you want to add the information just once, you can use raw sql (faster and no drawbacks), also you are right about the 2 tables (if the country is already in directory_country). If you want to make something that will be available for more Magento instalations you have to crate a new Magento module and add the sql using the installer you can read more here http://www.magentocommerce.com/knowledge-base/entry/magento-for-dev-part-6-magento-setup-resources
Magento wiki is a good place to start, also there are lots of blog posts.
It's considered a bad practice because Magento has its own ORM and most of the time for your new tables (entities) you only need to create models that extend magento core models and you will have access to CRUD without any development and everyone that uses your new module will understaind what's going on.
Example for a region you can use the class Mage_Directory_Model_Region or for a collection of regions Mage_Directory_Model_Resource_Region_Collection
I'm trying to build a data install script that I use to setup a new webstore. This script creates the categories, pages and static blocks and default settings for the specific shop (we use a multistore setup to host the shops). In our dev/staging setup this scripts runs great and all categories are build without any problem. But on our live system this script fails. After some debugging I found the difference is in the Flat catalog usage on the live systems.
The problem with creating the category with the flat tables enabled is in getting the parent path information based on the parentId given:
$parentCategory = Mage::getModel('catalog/category')->load($parentId);
Without flat categories enabled this gives a correct parentCategory, but with flat categories enabled it gives an empty object.
Why is this behaviour with flat categories enabled?
Maybe this behavior is because flat table(s) are not rebuilded after you create categories. Try to refresh indexes programmatically before getting $parentCategory .
Joomla 1.5 has JTable, which can be extended to act as an Active Record system (Create/Read/Update/Delete).
However, I can not find any way for this interface to create the table represented by my JTable sub-class.
Every example I have found has started with "manually create the database tables... ", then created a JTable class to work with it. I would like to be able to distribute my plugin and have it create the tables on setup, so that this is not necessary.
Any easy way to do this?
This is usually done in the install.sql of your extension (The link is related to component but I guess for plugins it's the same).