Hi,
I'm having an issue where I've created custom nameplates and I'm pretty sure I have all the required attributes, but when I go to run a nameplate report on the dwg, nothing shows up. Anyone else had this issue??
When I try to run the report it says "No Data to Display"
Solved! Go to Solution.
Make sure the nameplate drawing is in the active project when you run the report.
Also make sure you set "Project" instead of Drawing (all) or Drawing (pick).
I find the "Project" option is more reliable.
If you still have issues, shut down AutoCAD Electrical and Purge the Project mdb.
Its stored in:
C:\Users\<USER NAME>\AppData\Roaming\Autodesk\AutoCAD Electrical 2018\R22.0\enu\Support\User
It will have the same name as your project.
I hope this helps,
James
Hi Jim,
Thanks for the reply. The block has NP as the first two letters as well as the NP attribute.
Hi James,
Thanks for the reply.
1. Yes, the drawing is in the active project.
2. Setting the report to run on the Project didn't help.
3. What do you mean purge?? Do you mean for me to literally delete the project mdb file?? Sorry, I'm not sharp on MS Access.
Its the local Database that's created from the drawings in the project.
Its safe to delete, but if your worried about it just rename it.
it should force a rebuild on the database. the Database is used for the reports so if you get an error like you did, generally it means there is an issues with the database, so cleaning it out is the best practice.
Hi James,
Thanks for all the help, but the deletion of the project "Scratch" db did not work either... any other ideas??
See attached image, your symbol appeared in my nameplate report. It's the one with description 'blah blah'.
To me, this implies that perhaps it's something to do with your workflow. Can you detail the steps you use to place the nameplate?
Jim
Hi Jim,
Thanks for your help once again! I ended up asking our consultant (Spatial Business Systems) and we were able to fix it!!
THE SOLUTION WAS: My custom nameplate block needed BOTH attributes FP & NP in it. Prior, I had NP but not FP. So, once we used the ADD ATTRIBUTE button to insert FP, it showed up in the report just fine!
Thanks for everyone's help on this!
I am having similar issues in AutoCAD Electrical 2020. I have a nameplate that also carries the footprint for my pushbuttons. I do this so the button automatically uses the right nameplate format when I insert it. I added both attributes NP and FP. I use the schematic list to insert the footprint. ACADE then adds a bunch of XDATA to the footprint including VIA_WD_FP. It does not add the VIA_WD_NP XDATA. I would have thought it wouldn't add either since the NP and FP attributes exist. If I manually add this XDATA it shows up on the report. Did you have this issue?
My guess is, the XDATA for NP_XDATA isn't there because it needs to be pushed in from the nameplate command itself.
Remember, you're inserting a nameplate bundled together with a pushbutton footprint. The software adds XDATA based on the command it's running and you're not running the nameplate command. That said, I can't really think of any easy way of fixing this; every idea I have involves either changing your workflow, or the symbol, or both. And they only would work if you were able to invoke the nameplate command along the way, anyhow.
Without diving deeper, I'm willing to bet that doing anything else will take longer than how you're already doing it.
I was hoping that since the block has the FP and NP attributes, it wouldn't add the XDATA. I guess that's not the case when using the commands. Will it always add XDATA, or can I add enough attributes that it will skip adding XDATA?
XDATA and attributes aren't the same thing. Adding attributes won't affect a command that is specifically looking for XDATA. And it definitely looks like the nameplate report is one of those commands that looks at XDATA.
Likewise, you can't change whether or not a command adds XDATA - generally speaking, it's part of the compiled code for the command. And really, you don't want to prevent this anyway. The lack of XDATA in your nameplate footprint is already causing problems with the nameplate report.
You can add XDATA on your own, but that involves either: 1) Manually adding it with the XDATA Editor tool; or 2) a coded solution that you'll have to write and implement.
Since a coded solution already exists (the nameplate command, which you're not using), then it seems like you're already doing this the fastest way for your workflow.
Can't find what you're looking for? Ask the community or share your knowledge.