I'm trying to export products (csv) in Akeneo, but some records are missing in the output.
The missing records are all part of certain families within Akeneo and I am trying to find out why they are not exported.
I have already tail'ed the log files, and checked the log/batch/* files, however, according to the logs everything seemed to be ok.
The only differences I can see (in the product table) are the family id's, but I must be missing something.
Any idea's/clues are welcome!
Currently you can't export products without any category.
Categories were missing in the products, I guess these are obligated for a product to show up in the export.
Related
I am creating a data dictionary and I am supposed to track the location of any used field in a workbook. For example (superstore sample data), I need to specify which sheets/dashboards have the [sub-category] field.
My dataset has hundreds of measures/dimensions/calc fields, so it's incredibly time exhaustive to click into every single sheet/dashboard just to see if a field exists in there, so is there a quicker way to do this?
One robust, but not free, approach is to use Tableau's Data Catalog which is part of the Tableau Server Data Management Add-On
Another option is to build your own cross reference - You could start with Chris Gerrard's ruby libraries described in the article http://tableaufriction.blogspot.com/2018/09/documenting-dashboards-and-their.html
I want to migrate existing news from one instance to another one incl. relations to FAL and content elements.
What is the best practise? I tried T3D Export, but it needs too much memory. Is this the only solution or do you have better ones?
1st you can try to export smaller chunks.
2nd you can do the export by hand. But then you must know which records are involved and what files are involved. And you must handle uid-collisions!
Starting with a simple query for your news-records.
Then you need all related records: FAL, tt_content, categories
Depending on your tt_content records you might need further related records - typical: FAL
Then you need to identify all the files.
Before you import all the records: make sure the used uids are unused in your target installation. oherwise you need to modify your uids (e.g.: you can add a constant value of 10000 to all your uids)
Im using a Page (type Folder) to show all records with this pid. Is it possible group these records somehow? Theres a field in my DB called "vid", which contains the uid of some other records. I want the records in my folder to be grouped by this uid. Any suggestions? (Using Typo3 4.6.3)
Ok, then the simple answer is No. Grouping is not possible with the default backend list view module. You can sort, and search/filter there, but not more. You may write a custom backend module that does the trick for you.
What I could also imagine is to use the export function in the list module (there is a button somewhere) and then do the grouping with your favorite spreadsheet tool (like excel). Depending on how often you need this feature that may be a simple workaround that does not require and additional coding.
I have annoying issue with CR 2011. We are trying to upgrade from very old CR8.5 (DBF files are used as source(s) for the reports) to CR2011 and right now strange issue has appeared.
There are several fields on the report and all of them contain some data (as can be seen in the dbf file itself and/or in Browse Field Data) but few of them are never "shown" on the report. (If I, however, browse the data within the preview in CR2011 designer, I can see the data with no problem.)
This report uses two (non-linked) tables.
If I try to create a blank report, add these two tables & format the report again, I'll get what I expect (i.e. all fields shown on the report). (But this is not a solution as we have hundreds of reports.)
It does not matter if I (re)save report in latest format.
Everything is shown when using CR8.5 (designer or "runtime")
Has anyone experienced similar behavior and/or some tips where to look?
Non-linked tables are "less" supported than before (whole support for dbf files is limited). So the only correct solution is to link non-linked tables together. In my case, as the "free" table was parameter table. I had to simply add "paramid" to both tables (always set to 0) and perform the linking.
Edit: This was a bogus question. The problem was that I had quotes in my description field. The entire field should be wrapped in one set of quotes with none inside. Changed quotes to apostrophes to fix. Magento is working correctly.
I am using a Profile in the Import/Export section of my Magento admin to import a CSV document.
My description fields are very long (around 10k file size). Two issues are occurring:
On the published product, only the first 50% or so of the description is present.
The Magento system does not import the next column on the import document (brief description).
Does anybody know how to fix this?
The proplem is much more likley the application you export your product data with and which creates the CSV.
Did you check if the CSV contains the full description prior to importing it? Maybe the application only allows a certain amount of characters in a column and truncates the rest.
I believe I read there is a bug (not necessarily confirmed) in the CVS import if your 'short_description' is more than a sentence or two long, it causes problems elsewhere. You've got long, long descriptions, but you didn't mention how short, your short descriptions are. Could you try importing with a one sentence 'short_description', then see what happens.
I'm not sure the protocol of recommending a commercial product here, but there's a windows program (I run it in vmware) that does imports/exports with a direct connection to the magento database, skipping the long-winded dataflow api). I've imported products from there in much faster time frames without issue. I've never had to deal with long descriptions, though. It's not cheap at $200, but the time saved has been worth for it for me. It's the first result for 'magento manager' in google.
Have you confirmed by creating by hand a single product with a huge description that magento doesn't choke on it?