I am in need of showing "All Mails" that have been transacted in OpenERP 7 with no restrictions.
There seems to be some restrictions done when records are fetched from Database(postgresql).
Is there a way to show all the records available in postgresql directly?
Their are several ways, you can use any of below:
You can create Separate menu without any domain on mail.message object which will show you all the messages.
Also you can create the postgres view report for more statistical information on mail.message object this will be tricky and long but informative in future.
Or Even you can remove the Domain from the existing Email menu action to show all the record without any restriction.
Thank You
Related
I would like to implement a way to send an email notification (containing content of a log note) to all followers of a record for every log note of that record. I would also like to implement a way for email-replies to said email notifications to appear as log notes of that particular record.
What would I need to do to achieve this (at the back-end) or does Odoo already have a quick solution for this? I thought of creating a template, and overriding the _message_subscribe function to send its content as an email. Although I'm not sure how to go about linking email-replies back to the portal as log notes.
One of many solutions to this requirement is to set the mail subtype "Note" as default activated.
Those subtypes can be configured on record follower base. So every User can have it's own subtype configurations.
But to just set a default, this should easily work. I'm not a fan of the requirement at all, but atleast i'm a fan of the solution :-P
Just go to Subtypes menu (Settings -> Technical -> Email -> Subtypes) search for "Note" and activate field "default"
I have an internal table whose records I would like to show in a list when user clicks details icon in application log. I know I should pass program, form and table with records to the BAL_S_MSG t_par and callback elements but its not working. Anyone can direct me to a example?
thanks
Check the example programs provided in the package SZAL, for instance SBAL_DEMO_06 (although I'd strongly suggest NOT to use the REUSE function module used in that example).
I've got a lookup field on Account entity called something. Each such Something has a reference to an account. When my users click the magnifying glass, I want them to see a list of available Something records but filtered to view only such instances that link to the currently treated entity.
Also, I'll need to design such a filtration for Contact instances to only show the Something records that are related to the account that the currently regarded contact is a member of.
I can't decide between a plugin on Retrieve and some JS in OnLoad registering a fetchXML. All such operations will be done client-side. The solution needs only to work in CRM13 (and if possible apply some cool functionality in that version).
Suggestions?
JavaScript & FetchXml are your best option here as with a Retrieve plugin you're taking the performance hit of executing on every retrieve regardless of whether the entity is being retrieved for the lookup. A filtered lookup in JS only applies for those scenarios that require a change to the field on Account.
Another other good reason for using a filtered lookup in Js is they are now a supported feature in CRM 2013 as opposed to the "hack" that was required in 2011.
Some more info on addPreSearch and addCustomFilter can be found on MSDN and there's a decent blog post providing examples here.
The documentation for the Dynamics security model (msdn.microsoft.com/.../gg334673.aspx & msdn.microsoft.com/.../gg328567.aspx) states that in order to relate two records together a user needs Append To and Read privileges on the parent Entity and Append and Read permission on the child Entity.
In practice it seems like a Dynamics CRM 2013 subgrid will not let a user relate records unless they also have at least user level Create privileges on the child Entity. Using the Dynamics SDK to relate two records together works as expected, however when in the Dynamics UI, clicking on the '+' button to begin in a subgrid to relate two records together does nothing unless the user has Create privileges.
Curiously I've also noticed that while clicking on the '+' button does nothing, if I refresh the page afterwards I always get one of those "Dynamics has encountered an error" popups, perhaps this is a bug with Dynamics?
At any rate this is a pretty breaking problem for us as we have plenty of “reference data” Entities in an N:N relationship that users should be able to relate existing records with, but not create new records.
Is anyone else aware of this problem? Is there some kind of workaround or setting that I'm missing?
(Link to issue on Dynamics CRM forums: https://community.dynamics.com/crm/f/117/t/119729.aspx)
When you click on the "+" on the sub-grid your sub-grid may create a new record or may give you an option to associate a record, depending on how your child entity is configured. For completeness, I'll detail how to either get the option to associate or to create a new record.
To Give an Option to Associate
On the child (e.g. Contact) The look-up to the parent record (e.g Account) cannot be required. If the look-up is required CRM will automatically create a new form (Contact in this example) and pop it into a new tab/window. If this is your issue and you need the look-up to the parent to be required, you may want to make the look-up to the parent non-required and then require the field using on-load javascript.
To Create New Record & Pop into new Tab / Window
Require the look-up to the parent on the child account, or;
Hide the "Add Existing" button on the child record using your ribbon editor of choice
I raised this issue with Microsoft and they have formally recognized it as a bug. The fix is due to be released in Update Rollup 2.
It's a known bug and already fixed in update rollup 2
I'm building an order management system for customers. I need to set it up so I can build a form that emails a brief of the order status to a customer. The trick is that a customer can have multiple emails i.e no limits on that and the form I need to set up would show the brief generated in a textbox(nothing hard there) as well as a list of checkboxes with the email addresses which to send to.
Clicking on/off the checkboxes determines which addresses would the brief be sent to. I have everything worked out except for one main thing i.e the form - I'm not sure how can I actually set this part up i.e I'm using simple_form here and I'm not sure which model would I be making the form against? Do I need to build another model here? I'm pretty stuck.
May be you can create model like Email without database and use all ActiveRecord helper methods. These articles may be helpful.
http://yehudakatz.com/2010/01/10/activemodel-make-any-ruby-object-feel-like-activerecord/
http://railscasts.com/episodes/193-tableless-model?view=asciicast