I'm trying to attach a document to the opportunity. My question is
Can the note be altered so that only one file can be attached and not several?
some example?
You can write a plugin on Pre-operation stage of Annotation Create message to evaluate if there is an attachment already for that particular Opportunity & stop the execution by throwing InvalidPluginExecutionException exception.
You can attach only one file in each Notes entry. So this should work.
Related
Facing this issue and cannot identify the root of this error. Any inputs will be helpful.
When trying to add a new Order Product record associated with Order entity, I am getting the below mentioned Business Process Error. When trying with Admin user it does not give any error, but when trying using Standard User it given this error. Please find the related error statement.
P.S: Does this thing has anything do something with Plugin or Business Process Flows?
Thank You.
I think you have an plugin or workflows attached to this entity or related entity to it.
If you check into this direction it will help you analyze deep.
I'm new to SuiteScript. Is it possible for SuiteScript 2.0 to create a trigger to start some funcionality as soon as a new file is uploaded to a particular folder in Netsuite's File Cabinet (by web services or manually by drag and drop zone)?
Thanks in advance for helping me out.
I do not see that a server side User Event script can fire for the File object like it can for so many other objects. It is not listed in the "Applies To" field for a script's Deployment record.
Additionally, Workflows have a similar field called "Record Type", and it is not listed there, either.
If you are creating File objects via SuiteTalk, you can execute logic after the "add" method is executed synchronously, or you can call a RESTLet if you would like to execute logic server-side in NetSuite.
I am testifying soon as to data I gathered using MFCMAPI in which I determined that the PR_LAST_MODIFICATION_TIME did not match the PR_CREATION_TIME or PR_MESSAGE_DELIVERY_TIME of the message.
What actions in Outlook would cause PR_LAST_MODIFIER_NAME or PR_LAST_MODIFICATION_TIME to be modified? Simply reading, marking the message as unread, and viewing the attachments does not modify these properties in my lab tests.
I am trying to determine what other actions performed by the user or on behalf of the user could cause the PR_LAST_MODIFIER_NAME to no longer list the sender and PR_LAST_MODIFICATION_TIME no longer match Delivery/Creation time.
I had the opportunity many months ago to talk to developer on the MFCMAPI project from Microsoft and I am kicking myself in the gut for not writing down his name.
Any help is appreciated.
Do you mean Steve Griffin?
I am not him, but I think I can easily answer your question - every time IMessage::SaveChanges is called, PR_LAST_MODIFICATION_TIME will be reset.
I have a simple plugin for a custom entity that is set to trigger on Update of my custom entity. It is registered in the Post Operation stage. I have noticed some strange behaviour when I make changes to the Owner field of the record in addition to other standard fields (e.g. text boxes, dates etc).
The plugin fires the first time and the only attributes that come across in the image are all the regular fields. The owner field does not come across.
The plugin then fires again, but the Depth property of the context is still only one (i.e. the plugin is not getting triggered by changes made in the plugin code). In this run of the plugin, the attribute that come across is only the Owner field.
My theory is that because the owner fields are 'special', the CRM is doing two different requests - one to change the regular fields, and then another request for changing the owner via an AssignRequest. However, I cannot find any 'official' documentation for this behaviour.
Can someone explain why this is happening?
I am running Dynamcs CRM 2013 UR2
The Update event fires during the Assign event. So if an assignment takes place your plug-in will execute. The same is true for SetState - if you activate/deactivate a record an Update event takes place. These items are not documented in the SDK.
A good practice is to use Attribute Filtering on your Update plugin so it only fires for the fields it is concerned about - this will, assuming it is isn't looking at the owner related fields, avoid it firing twice. If you have logic specific to record ownership you would put it in a plugin that is registered on the Assign event.
I was not able to find official documentation about this, but I think Assign message is what you are looking for (if the entity is user-owned. See http://msdn.microsoft.com/en-us/library/gg328576.aspx. I would strongly recommend that you specify Filtering Attributes if you are registering a plugin on Update message. You could also debug your plugin and inspect MessageName property of plugin context and see what message gets triggered. I hope this helps.
I'm relatively new to the CRM SDK, and I'm trying to write a plugin to alter From/CC fields of an email on Create. It seems when this is registered in Pre-operation, the ActivityParty collection cannot be modified(though things like subject and body can be modified), and this post recommended setting the pipeline stage to Pre-validation.
When I do this the plugin no longer gets triggered. I know this because when remote debugging, breakpoints are only hit when pre-operation is selected. Also, when not remote debugging, none of the other changes get implemented in the plugin code.
Does anyone know what might be preventing this plugin from executing?
When you register plugin on Create message fields To, CC, BCC will be empty. Try register on DeliverIncoming / DeliverPromote messages