You change “Plush Otter (Small)” to “Small Otter Plush,” click save, and Altru answers with a short, unhelpful message: Parameter is not valid. The name you typed is fine. Nothing about it looks unusual. So what is Altru objecting to?
The short answer: the message usually isn’t about the name at all. It’s a generic error passed up from the software underneath Altru, and it tends to point at something else on the record that gets re-checked when you save. Below is what that wording typically means, the things worth ruling out, and how to get the change made even if the root cause takes a while to pin down.
What “Parameter is not valid” usually means
Altru is built on Microsoft .NET. “Parameter is not valid” is a stock .NET message, and it is best known as the error .NET raises when it is handed image data it can’t read: a corrupted file, an unsupported format, or a picture that was saved incorrectly. It is not a message Altru writes to explain a business rule, which is why it doesn’t tell you which field is the problem.
That matters because saving a rename usually means saving the whole record. Any field on the merchandise item, including one you didn’t touch, can be read and validated again when you click save. If one of those fields holds something the system can’t process, the save fails and you get the generic error, even though the only thing you changed was the name.
We can’t say with certainty which field triggers it in every case. Blackbaud hasn’t documented a single cause that we can point to, so treat the list below as a set of likely suspects to test, not a confirmed diagnosis.
Things to rule out, most likely first
1. An image attached to the item or its product
Given what the error usually means in .NET, start here. If the merchandise item (or the product it belongs to) has a picture, try saving the rename on a similar item that has no image. If that works, the image is the likely problem. Re-saving the picture as a standard JPG or PNG at a modest size and uploading it again, or removing it temporarily, is a reasonable test.
2. Characters copied in from somewhere else
Names pasted from a vendor spreadsheet, a POS export, or an email can carry invisible characters, curly quotes, em dashes, or trailing spaces. Type the new name by hand instead of pasting it and see if the save goes through.
3. Length or uniqueness limits
Very long names, or a name that matches another item, can fail validation. Usually Altru gives a clearer message for these, but it costs nothing to try a shorter, clearly unique name as a test.
4. Older data on the record
Items that were created years ago, imported during a conversion, or edited through an integration sometimes carry values that the current version of the edit screen doesn’t like. If renaming a newly created test item works but renaming an old one fails, that’s a strong hint the issue lives in the old record’s data rather than in your workflow.
5. Browser or session issues
Less likely, but quick to eliminate: clear your browser cache, try a different supported browser, or have another user with the same rights try the same rename. If it works for someone else, the problem is on your machine, not the record.
A clean way to test without guessing
- Note exactly which item fails and copy the full error text, including any details link.
- Try a trivial rename on the same item (add one letter). If even that fails, the name isn’t the cause.
- Rename a different item from the same product. Then rename an item from a different product.
- Create a brand-new test item with no image and rename it.
- Compare what the failing item has that the working ones don’t: an image, unusual attributes, an older creation date, an import history.
Fifteen minutes of this usually narrows it to one or two candidates. If your organization has a sandbox or test environment, do the experimenting there rather than in live inventory.
When to call Blackbaud support
If none of the above clears it, open a case. Generic .NET errors are exactly what support can trace on their side, because they can see the underlying exception that the screen doesn’t show you. Send them:
- The item name and its product
- The exact error text and the time it happened
- What you already ruled out (image, pasted text, other items, other users)
- Whether a new test item renames without trouble
That last point helps them more than anything else, because it separates a data problem on one record from a broader bug.
Getting the item named correctly in the meantime
If the rename is blocking you before an event or a store reset, one option is to create a new item with the correct name and stop selling the old one (mark it inactive if your setup allows it). Before you do that, think through the tradeoffs:
- Sales history stays with the old item. Reports and queries that look at a single item will show a split. Note the change somewhere your finance and retail staff will see it.
- Inventory counts don’t move automatically. You’ll need to adjust stock on both items so on-hand numbers stay accurate.
- Anything that points at the old item, such as barcodes, register setups, or price lists, needs to be updated to the new one.
For one or two items that’s manageable. If the error appears across many items, hold off on workarounds and let support find the cause first; recreating a whole catalog creates more cleanup than it saves.
Quick answers
Is my item or inventory data damaged?
Not necessarily. The failed save means the change didn’t go through; it doesn’t by itself mean anything on the record was lost. Check the item afterward to confirm it still shows the old name and stock.
Will removing the image lose anything important?
Only the picture itself. Keep a copy of the original file before removing it so you can re-upload a cleaned-up version later.
