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?
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 hope my question makes sense, I'll try to give as much info as possible.I should probably start off by saying this is the first access database (any database) I have ever done and my knowledge comes from trial and error as well as youtube and the occasional google search...NOOB
So I'm attempting to build a database using microsoft access (2007) for the first time (Student Records in my department). I have pulled in all the data I had available (names, major, graduate, advisor etc.) and made several appended tables for additional data using an append query (usually just pulling over name and ID# and major, and then adding the information that is related to the particular table).
Now I am going through the paper files (which we would like to get rid of) to update any missing data or add new students that we didn't have stored anywhere electronically.
I have created a form in which I can add new records or edit/add already available data that I need.
The problem that I have is that it pretty much pulls up everything I need except the occasional record (which I do a search in the search field on the bottom using the ID#) so I figure hey I must not have this student and add it, when I hit save it basically tells me this record can't be added as there already is a conflicted value. And when I check my table sure enough the record is there. In the form query where I check what tables the field's information is pulled from I have no criteria in there to filter any information out, the relationships overall are just based on the ID# (which is my primary key in all tables). When I check the data everything seems to be correct (not a wrong major, etc.) so I can't quite figure out why some records are not being pulled up.
My question is why and what can I do to fix it...
I hope my explanation is not to confusing. Thank you in advance.
I am trying to move sugarCRM data (Leads, Opportunities and Applicants, these are modules in sugarCRM) - I have the .csv files. No SQL.its hosted by this company and they won't give me the sql.
the issue is that leads for example has 212 columns(fields)
the regular sugarCRM has far less fields.
I am trying to figure out what is the best way to import all the data without having to use the Studio to create each field individually.
Opportunities module has 110 fields also on the hosted version - and the regular sugarCRM only has about 27.
so my question is how do I create all the fields so I can import them
I already created a file that gets the column names, and I did import all the data into a table called Leads1. when I rename it to leads and check ... the data doesnt show on the page.
any ideas? (please dont answer and say : ask the company to send you the sql, because they will not send it they know I want to move out of their hosted environment I already spent an hour on the phone and they wouldn't)
any ideas or suggestions would be greatly appreciated thank you
With or without the SQL you'll need to recreate the fields in Studio as you need the views to also include the fields. It's tedious, but the only real viable option in this case. It is important that the fields are named exactly the same when doing this so that the import works correctly.
If you can hack some code, another option is to create a module that will export the SQL for the whole database for you from within SugarCRM and also the whole file structure as a zip so that you don't have to recreate anything.
BTW - make sure that the SugarCRM instance you are moving to is the exact same version. Once you do the import then you can upgrade to your desired version. This guarantees that the DB structure will be the same then (given that the custom fields get created appropriately).
Good luck!
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.
I want to import old blog posts into Orchard CMS's blog module.
These are not contained in any xml format, if I try to add them manually then my posts display by creation date which ruins the order of original creation date of my blog. I noticed with Windows Live Writer I can set the Publish date but this still does not effect the Creation date.
There is a module called BlogML, but my blogs are not in RSS format. I see the BlogML.xsd is here http://blogml.org/, but is there some software I can use to generate the correct XML which I can then import into Orchard? And will this fix the creation date at all? I think I may be left in creating a custom type say 'imported blog' and add extra fields on which I can sort by.
If you are so worried about the creation date, you could just go into the database manually and change the creation date for each blog entry. Would take a lot less time than anything else.