EdBundy - Tuesday, July 17, 2012 8:03 AM:
Good day
We are evaluating Aras, and part of the evaluation is to determine the configurability of the software. One of the additions I am making is to add an item type to keep track of memo's sent to and from the company. I have created the item type and forms, and can access the form through the TOC and add the memo instance. However, when I try to add a file relationship to the memo instance, I get the following error:
Object reference not set to an instance of an object
This has got me baffled, I have also tried to use the "document" item type as a template, did a "save as" (and it created a lot of "copy of copy of" labels), but got that working too - I can add a "Temp document" instance to the item type, but cannot add a file (when I do, I get the error above).
Has anyone seen this error, and what is it's cure?
Sorry for the totally novice post, but in my defence, I am a ME :-)
Thanks in advance,
Ed
nbrown - Tuesday, July 17, 2012 11:09 AM:
Hi Ed,
How are you adding the relationship to the 'Memo' Itemtype? You can create a new relationship to 'File' called 'Memo File', and use that.
You need to make sure that your Vault is setup properly (can you add/view files to the document object?)
~Nate
EdBundy - Tuesday, July 17, 2012 4:14 PM:
Hi Nate
Sorry for my late reply - I have added a relationship type (and its accompanying item type) that defines a relationship between the "Memo document" (which is similar to the "Document: item type) and "Files", much in the same way as "Document Files" relate "Document" and "Files". The vault is set up properly - I can add, revise, track both "documents" and "CAD documents", so I don't believe that is the problem. My issue is that the error code is so generic, I've got no idea where to start looking.
What I have done, while creating the relationship/item types for the memo, is use the server actions as was defined in the "document files" types, because I wanted to retain the incrementation functionality. I have very little knowledge of coding, so I may have made a mess there (I read elsewhere that this error is normally code-based, and due to incorrect code/variable use)
This description may be clear as mud, but I was hoping that there is a way to determine what process/code/action call is causing the error.
I will try disabling some of the server actions to see if that was the cause.
Thanks for the help!
Ed
nbrown - Wednesday, July 18, 2012 9:11 AM:
Hi Ed,
For the memo, just relate to the file itemtype, and don't use any methods- unless you want some sort of identifier other than the standard ID given to the files.
If you still want to use that server event, you will have to create a new method that utilizes the newly created itemtypes and relationship types. The error you are getting is from the method- you can debug it with a debugger, which will give a more specific error. Hope this helps!
Disabling the actions should work for you.
~Nate
EdBundy - Wednesday, July 18, 2012 11:07 AM:
Hi Nate
You are spot on - the "inherited" methods call the standard "document file" item and relationship types, and I'm using custom ones. Removed all methods and file addition worked fine, added some custom methods (based on the originals, but referencing the new item types) and it worked fine. Seems the error was related to the script calls.
Resolved!
Thanks a bunch for your help!
~Ed