Actions
Forum Thread Details
  • State Verified Answer
  • Locked Locked
  • Replies 25 replies
  • Subscribers 88 subscribers
  • Views 4206 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New feature is 1.5 - Can't export BOM's to Excel

Sparkylabs

i can no longer export BOM's in excel format. If i use the template I used to use in xlsx format CS now cannot work with this. having converted my template to XLT excel cannot handle the output from CS. So new version and MORE bugs.

 

Where do I send my invoice for the time I am wasting on this software? some of us have businesses to run!

Parents
  • 0

    It has happened on two different projects on two different computers. the only commonality is that the BOM is for a project variant.

     

    No I can't change the text format in excel. Even if I do as you suggest it retains the formatting in floating paint notation even though it would no longer be recognised as such the original part number is destroyed, it has to be "imported" in order to not try and be clever.

Reply
  • 0

    It has happened on two different projects on two different computers. the only commonality is that the BOM is for a project variant.

     

    No I can't change the text format in excel. Even if I do as you suggest it retains the formatting in floating paint notation even though it would no longer be recognised as such the original part number is destroyed, it has to be "imported" in order to not try and be clever.

Children
  • 0 in reply to Sparkylabs

    All the CSV file fields should be in quotes by default so they don't get 'smartly' converted. For example:

     

    "FS1","FUSE LITTLEFUSE POLYFUSE 2200mA 30V THRU-HOLE","1","Farnell","1175-844","",""

     

    So, "1175-844" doesn't get converted to 331.

     

    Did you add extra quotes around the Wurth part numbers? Or maybe there is some escape char in the part number?

  • 0 in reply to voltsandjolts

    Also, I don't use variants so maybe there is an issue there, as you suggested.

  • 0 in reply to voltsandjolts

    Look CS offer output in CSV it should format the file appropriately, I'm not going to re-edit the BOM everytime I export it. Basically the whole BOM export is buggy.

  • 0 in reply to voltsandjolts

    Well I need variants in these projects as they are designed to have a common PCB with options.

  • 0 in reply to Sparkylabs

    If you are creating the BOM in CSV format then the trick is to read it into Excel correctly. Do not just open the file otherwise it does tend to mess up things that look like numbers or dates, it is a complete pain the way it messes up data. Use the import option instead - a good randomly found link on the subject if it helps https://www.hesa.ac.uk/support/user-guides/import-csv .

  • 0 in reply to Sparkylabs

    Look I didn't suggest you re-edit the BOM!

  • 0 in reply to voltsandjolts

    Yes importing the data to excel solves it. However CS is unable to read or write excel formats as claimed.

  • 0 in reply to Sparkylabs

    Hi Sparky Lab's,

     

    The templates haven't changed between CircuitStudio version 1.4.x and 1.5.

     

    I've just made a basic Excel template that the data for the component in the example file loads correctly when the BOM data contains an extra " character that isn't escaped, e.g.:

    2x5 Pin Header 0.1" Header, 2x5, 0.1", Straight, Vert HDR2 HDR2X5 D-300-0163-1 1

     

    The CSV text file contains two double quote characters "" in a row, so the columns will be incorrect for that component. Loading via Excel doesn't have this problem. Is this a similar problem to what you're seeing?

     

    I linked the BOM Basic Template.xltx template file that I made, but please unzip before using. The default location is C:\Users\Public\Documents\Altium\CS\Templates

    https://www.dropbox.com/s/hs7zik49s68q5ub/BOM%20Basic%20Template.zip?dl=0

     

    Best regards,

     

    James Harriman

    Altium

    image

    image

  • 0 in reply to jamesharrimanaltium

    Hello James. The problem is not the CSV file export, the problem is that YOUR software will not do as it purports to do (product sold is not to description/self professed functionality). CS in 1.41 or 1.5 will not work with excel file formats. In the past a standard excel file was acceptable now it has to be in excel template format. So having gotten over that hurdle the excel file that CS puts out cannot be opened by excel. So the treatment of an excel format in CS is non functional.

     

    I have this on 3 different computers!

     

    CSV export works fine as it involves no excel templates. The problem was that excel is trying to be clever and to get round this I have to import the data to excel rather than open the CSV directly as Peter pointed out.

  • 0 in reply to Sparkylabs

    Hi Sparkylabs,

     

    So it's not just a component that's being displayed incorrectly in Excel? But rather, the files won't load at all? The BOM templates in Altium Designer and CircuitStudio have always been Excel Template format, i.e. xlt or xltx format, not worksheet, i.e. not xls or xlsx. So I don't understand your observation that "In the past a standard excel file was acceptable now it has to be in excel template format.".

     

    I think it could be the specific files with problems rather than changes in the software, so if possible it would be good if you were able to send in your xlt or xltx with the problem to Element14 support for investigation.

     

    Did you try the BOM Basic Format.xltx file I linked to?

     

    Best regards,

     

    James Harriman

    Altium