What is the limit number of characters a filename can have?
What is the limit number of characters a filename can have while uploading to RRC?
Thank you |
6 answers
What is the limit number of characters a filename can have while uploading to RRC? Hi Eduardo Which version of RRC are you using? If you're running into issues here you may be hitting an operating system limit for 3.x versions. |
What is the limit number of characters a filename can have while uploading to RRC? Hi Eduardo Which version of RRC are you using? If you're running into issues here you may be hitting an operating system limit for 3.x versions. Hi, Chris. The problem has been identified in RRC 2.0, but it would be good to know the limit for 3.0 once we're in the subject. Thank you |
Hi Eduardo,
For 2.x, the name eventually gets stored as an indexable field and that effectively determines the limit. As I recall, the limit was 1024 bytes, so in terms of characters, it depends on the type of characters in the name (ie, does it include double-byte characters, etc). So you mentioned an "identified problem". Can you be more specific about what problem you're encountering? |
Hi Eduardo, Hi, what happens is that if the filename is too long, if the user tries to link the document to an artifact, they click the OK button in the "Link to" window and nothing happens. When they shorten the name, the link is made. Thank you |
Hi, what happens is that if the filename is too long, if the user tries to link the document to an artifact, they click the OK button in the "Link to" window and nothing happens. When they shorten the name, the link is made. Ok, so the problem is when creating links, and not necessarily when uploading artifacts with long names. I have two suggestions on how we can proceed with this: 1) When creating the link via the "Link to..." dialog, enter a Link Description. This will prevent it from constructing something by default based on the artifact name. 2) When a dialog appears to do nothing, it may mean an exception has occurred and that exception can be found in the log file. You would tyupically find the log file here: C:\Documents and Settings\{Windows login}\IBM\RequirementsComposer\workspace\.metadata\.log It's usually more helpful to delete that file first, then recreate the problem and provide us with the resulting log file. That way, it contains information just about recreating the problem and not months of other activity. If you find an exception in the log file, you can either share that here or go ahead and open a defect work item. |
Hi, what happens is that if the filename is too long, if the user tries to link the document to an artifact, they click the OK button in the "Link to" window and nothing happens. When they shorten the name, the link is made. Ok, so the problem is when creating links, and not necessarily when uploading artifacts with long names. I have two suggestions on how we can proceed with this: 1) When creating the link via the "Link to..." dialog, enter a Link Description. This will prevent it from constructing something by default based on the artifact name. 2) When a dialog appears to do nothing, it may mean an exception has occurred and that exception can be found in the log file. You would tyupically find the log file here: C:\Documents and Settings\{Windows login}\IBM\RequirementsComposer\workspace\.metadata\.log It's usually more helpful to delete that file first, then recreate the problem and provide us with the resulting log file. That way, it contains information just about recreating the problem and not months of other activity. If you find an exception in the log file, you can either share that here or go ahead and open a defect work item. Thank you, Stef. I'll ask the customer to tr that and I'll get back to you. Thank you |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.