Create below three User Lookup fields Account-
Assigned Attorney
Assigned Paralegal
Managing Attorney
When an event is created, automatically add each of the users in these specific “fields” on an account as an attendee to each event at the point the event is created;
Assigned Attorney
Assigned Paralegal
Managing Attorney
For all future events on an Account calendar, when an assignment in one of the three fields below changes, automatically update the attendees on the event, removing any removed attendees and adding any added attendees.
Assigned Attorney
Assigned Paralegal
Managing Attorney
actually i am trying in this screen flow and I make 3 lookup field relation with user object. After i make the event but this sends error
Related
In my database I have a tblCrewInformatio related one-to-one to a tblCouserExpireDate (Auto filled from another source and no edition available).
Not all Crew have Course information (because they are new at the company)
In my Form I get tblCrewInformation and associate with the process of Flag Registration Requirements (A check list of documents we must attend to submit the registration) In this form I have a field blocked that show the expiration date of the courser, this way before I check the document as "ok" I see if it still valid.
Access doesn't let me Create a Flag Registration for a Crew Member that doesn't has a tblCouserExpireDate data.
I tried to uncheck "enforce referential integrity" or change the join type, but it didn't change the status.
I have been banging my head against the wall for a while trying to get this to work.
I have an Access 2013 database. The db has a subform with a RecordID, Business Name, and Primary Contact in a continuous form.
I have the active record being highlighted at this point.
The RecordID, Business Name, and Primary Contact fields are being passed up to the parent form so they can be used later for other sub-forms/purposes. I have a text-box in the middle of the parent form that I want to show the active record name in.
If the business name is empty I want to display the primary contact name and if the primary contact name is empty I want to display the business name.
I have gotten the if statement to work if i put the code in the OnClick event and I click on the RecordID text-box. Is there a way to trigger the event when the RecordID automatically changes without my interaction with the RecordID text-box.
the easiest way to do this is to set the control source of the ActiveRecordNameTextBox to an expression. Experience tells me you probably tried this but had trouble referring to the subform. I always have to use areference when I refer to subforms. Here is a reference that also gives some explanation:
https://www.fmsinc.com/tpapers/primer/index.html
if and only if is a natural choice for the expression given you want to select between two values. So if you want to refer to the subform controls use something like:
=IIf(IsNull(Forms!MainFormName![SubFormName].controls("BusinessNameTextBox")),Forms!MainFormName![SubFormName].controls("PrimaryContactTextBox"),Forms!MainFormName![SubFormName].controls("BusinessNameTextBox"))
You could also refer to the subform recordsource fields directly. Also when refering to a subform from the mainform you can use relative references to get:
=IIf(IsNull([SubFormName].[Form]![BusinessName]),[SubFormName].[Form]![PrimaryContact],[SubFormName].[Form]![BusinessName])
Note since you weren't explicit about the edge cases Like what to do if you have both a BusinessName and a PrimaryContact I just picked displaying the BusinessName if available and nothing if both where blank.
After the user grants me access to his calendar I would like to create a calendar dedicated to my application, so as not to litter users primary calendar. But if the same user grants the access the second time, the second calendar with the same name gets created, and so on. How can I check if the calendar already exists?
CalendarList returns a list of all of the calendars a user has access to. It basically the list displayed on the left hand menu, in the web application.
You can do CalendarList: list to retrieve a list of all of the calendar a user has then scan through the list to see if your calendar exists already.
I want to create a multi-select Contact Lookup.
What i want :
When user clicks on a lookup then he should be able to select multiple contacts from that.
What i have done:
I have created an object and a field inside that object using both
"Lookup" and
"MasterDetail Relationship" and
"Junction Object"
When i try to use this Field for any input text/Field then it always provides an option to select only one value from lookup but i want to have an option to select multiple.
Even in the Junction object i have created 2 master-detail relationships still lookup allows only one value to be selected.Moreover it makes the field mandatory which i don't want.
Links that i followed:
http://success.salesforce.com/questionDetail?qId=a1X30000000Hl5dEAC
https://ap1.salesforce.com/help/doc/user_ed.jsp?loc=help§ion=help&hash=topic-title&target=relationships_manytomany.htm
Can anybody suggest me how to do this.
Its same as we use Email CC/BCC under Send Email option for any Lead.
Even you use a junction object a lookup is just that, it references (looks up to) one other record: when you create a record on the junction object you still have to set each lookup individually and you're still creating only one record.
Master Detail relationships are essentially lookups on steroids, one object becomes the child of the other and will be deleted if the parent object is deleted, they're not going to provide an interface to lookup to many records at once.
If you're not a developer then your best bet is to either just create on junction object record at a time, or look into using dataloader. You could prepare your data in Excel or similar and then upload all the records into Salesforce in one go.
If you are a developer, or have developers at your disposal, then what we've done in the past is create a Visualforce page to do the job. So if, for example, you wanted to link a bunch of contacts up to an Account, we'd have a single account lookup field on the page, then some search fields relating to fields on the contact. Using a SOQL query you can then find all contacts matching the search parameters and display them in a list, where you may want to provide checkboxes to allow the user to select the contacts they want. Then it's just a case of looping through the selected contacts, setting their Account field to be the chosen account.
There are areas in Salesforce (such as the send Email functionality you mentioned) where it's clear to see that bespoke work has been done to fulfil a specific task — another instance of what you want is in the area where you can manage campaign members. This is the model I've copied in the past when implementing a Visualforce page as described.
Good luck!
For adding multiple junction objects at one time, the only solution we have found is a custom Visualforce page, as described by LaceySnr.
For a slightly different problem, where we need to assign many of object B to object A, We have trained our users to do this with a view on object B. We are assigning Billing Accounts (B) to Payment Offices (A). The view on Billing Account has check boxes on the left side. The user checks the Billing Accounts to be assigned, then double-clicks on the Payment Office field on any of the checked rows. A pop-up asks if you want to update only the single row or all checked rows. By selecting 'all checked rows', the update is done to all of them.
The view is created by the user, who enters the selection criteria (name, address, state, etc.). All user-created views are visible only to them.
Let's say you have two kinds, Message and Contact, related by a
db.ListProperty of keys on Message. A user creates a message, adds
some contacts as recipients, and emails the message. Later, the user
deletes one of the contact entities that was a recipient of the
message. Our application should delete the appropriate Contact
entity, but we want to preserve the original recipient list for the
message that was sent for the user's records. In essence, we want a
snapshot of the message entity at the time it was sent. If we naively
delete the contact entity, though, we lose snapshot integrity; if not,
we are left with an invalid key.
How would you handle this situation,
either in controller logic or model changes?
class User(db.Model):
email = db.EmailProperty(required=True)
class Contact(db.Model):
email = db.EmailProperty(required=True)
user = db.ReferenceProperty(User, collection_name='contacts')
class Message(db.Model):
recipients = db.ListProperty(db.Key) # contacts
sender = db.ReferenceProperty(User, collection_name='messages')
body = db.TextProperty()
is_emailed = db.BooleanProperty(default=False)
I would add a boolean field "deleted" (or something spiffier, such as the date and time of deletion) to the Contact model -- so that contacts are never physically deleted, but rather only "logically" deleted when that field is set. (This also lets you offer other cool features such as "show my old now-deleted contacts", "undelete" functionality, etc, if you wish).
This is a common approach in all storage systems that are required to maintain historical integrity (and/or similar requirements such as "auditability").
In cases where the sheer amount of logically deleted entities is threatening to damage system performance, the classic alternative is to have a separate, identical model "DeletedContacts", but foreign key constraints require more work, e.g. the Message class would have to have both recipients and deleted_recipients fiels if you needed foreign key integrity (but using just keys, as you're doing, this extra work would not be needed).
I doubt the average user will delete such a huge percentage of their contacts as to warrant the optimization explained in the last paragraph, so in this case I'd go with the simple "deleted" field.
Alternately, you could refactor your Contact model by moving the email address into the key name and setting the user as the parent entity. Your recipients property would change to a string list of raw email addresses. This gives you a static list of email recipients without having to fetch a set of corresponding entities for each one, or requiring that such entities still exist. If you want to fetch the contact entities, you can easily construct their keys from the user and the recipient address.
One limitation here is that the email address on an existing contact entity cannot be changed, but I think you have that problem anyway. Changing a contact address with your existing model would retroactively change the recipients of a sent message, which we know is a problem.