I've Audience created in Mailchimp with only three merge fields namely First Name, Email and Phone. Now I want to add a new merge field but whenever I click on add new field it shows this specific error.
"A Merge Field with the tag "" already exists for this list."
I searched almost every forums but can't find any solution. I'm new to mailchimp.
Related
In mendix i have 2 pages: Course Overview and Course_newEdit.
As the names suggest overview i the overview page and the second one is edit page.
The entity name is Course.
Its attributes are: Name String and Description String.
I have a requirement that i when a user edits course, the default value for name should be the last user input value.
So if the user has give first course name as History.
The second time any user tries to input the name, it should by default show History.
how can this be achieved?
I couldn't find any option for the same in the default settings.
Mendix 9.2 pro
If you are editing an existing course than it will automatically show the value that was last stored in the database so you don't need to do anything there.
If you are creating new course and want the default value of 'Name' attribute to be automatically filled in using the previous course object, than you have to retrieve last saved course object from database with range option = 'First' and add sort property that can identify the retrieve object as last saved course object. Than you can use retrieved last saved course and copy 'Name' to your new course object.
Please check out Mendix Forum and Mendix Slack Community if you have more questions.
Mendix Forum: https://forum.mendix.com
Community Slack: https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ
first you need to retrieve the list "Course" from database then sort the list by creating date descending then retrieve head of the new sorted list then fill this object in the new created one
course/name
I have added a field to the Contact entity called Website Downloads. This field is updated every time a client clicks on our website but what I want to do is have a sub grid within the Contact form that shows what this entry is each time it's updated. Then I ideally need this in a view with the contacts name and a list of the downloads so I can do an advanced find on the field. Any ideas please. PS I have tried to add a new entity that links to this field but the problem is you cannot do an OR on an Advanced find for 2 separate entities so back to square one.
Already tried a new entity but this won't work as you cannot do an OR on an Advanced Find for 2 entities.
I think you are on right track. You need a related entity to capture all the website hits, then you need a rollup field on contact record to sum up the hits.
So the associated records can be listed in a subgrid on contact form, also Advanced find queries can be done.
Rollup field can be an OOB field but it has timely job to calculate, if you want immediate rollup result it can be a custom field & plugin to accumulate.
I am trying to add a field to my entity call abc_salespersonname when I try to add it I am presented with duplicate field name.
The field does not show in the solutions entity field list but I can see it in the database.
I do know that when you delete a field from an entity, it does not actually delete from the database.
So my question is, how can I bring this field in the database back onto the entity.
You cannot Undelete any field in a supported way. Once deleted is deleted, gone forever.
Not sure, if you are mixed up with “Remove” & “Delete” options within solution sub-components. Atleast “Publish All Customizations” will make all the database schema, Metadata & UI in sync. Verify the default solution by going to Settings->Customizations->Customize the system to double check.
If you are seeing duplicate field name alert, then you cannot bypass it. Create a new field with different name & move forward.
I have the UNID of a Lotus Notes form. can i use this UNID to get the Document Collection of that form ??
I am using the NotesDatabase.Search() method to get the document collection. But this query only works if it is provided with the Form Name. Does not works works with the Form UNID.
I am trying to do this because in my application there are two forms with the same name and Alias name.
Short answer: This is NOT possible.
Documents are linked to the Form via their own Form- item. This is a textitem and contains the alias of the form they were created with. There is NO further relation between the form that was "really" used when creating a document. As soon as you create another Form with that alias and delete the old one, all documents will use the new one. As long as there are 2 forms with the same alias, one of them will be used by chance (usually the one with the smaller NoteID will be used, but this can not be guaranteed).
If your question is to find out, which documents where created with which of the forms the only possibility is to select them according to special fields in the forms. If e.g. one form has an item "CreatedDate" and the other does not, then you could select #IsAvailable( CreatedDate )
Unfortunately if you open a document that was created with the "old" form and save it, it will also have the new item... So this will never be a 100% solution.
To make it even harder: One could create a document using LotusScript and in the end just fill the Form- item: doc.Form = "SomeForm". Then the document was not created with either of your two forms...
I'm trying to build a FileMaker Pro 11 layout that excludes records containing a certain value. The relevant data is in table Invoice. I want to filter so that Invoice records whose "Invoice Check Grouping" field is blank are not displayed on the layout.
I've added a global field to the invoice table called "Blank Invoice Check Grouping" to use as my filter criteria. I've created a self-join relationship to the Invoice table, joining "Invoice ID" to "Invoice ID" and joining "Invoice Check Grouping" to "Blank Invoice Check Grouping". The resulting table is named "Invoice Check Groupings".
The layout which I build based on table "Invoice Check Groupings" shows all records in Invoice--it does not filter out those with blank values. What am I doing incorrectly?
Thanks,
Ben
Layouts show records in a table (or more accurately, a table occurrence) and don't directly deal with related data. As mentioned by #pft221, you can use relationships for filtering, but only when viewing data through a portal.
If you always want a particular layout to show data based on a particular find, you can do so with a script and a script trigger. First set up a script to do the following:
Enter Find Mode[]
Set Field["Invoice Check Grouping"; "*" // Find all records with any data in this field
Perform Find[]
Note that you can also embed the find request within the Perform Find script step, but I tend to script finds in the above manner as it's easier to see what the find request is in the script and variables can be used in the find request.
Now you need to set your layout to execute this script whenever it's loaded. Go to the layout and enter Layout Mode. Select Layouts>Layout Setup from the menu bar. Click the Script Triggers tab and check the box for OnLayoutEnter and select the script you wrote above. Now whenever the layout is entered, that script will run and exclude the records that have that particular field being empty.
There are many ways to filter records, depending on what you are trying to do and what you are trying to display for your users.
The most common and simple way you can filter records is through a simple Find in a list view. I'm unclear from your question, but my best guess is that you're already using a list view and misunderstanding how FileMaker's relationships and Table Occurrences (TO's) work.
To Filter with the "Find Records" method:
Create a new List View layout of any Table Occurrence of your Invoice Table -- most likely you will want to use the default Table Occurrence that FileMaker created for you when you created the table.
Place the fields that you would like to display on that layout, including the "Invoice Check Grouping" field.
Switch into Find Mode
Put a '*' character into the "Invoice Check Grouping" field
Perform the Find
You should now see a list of all Invoices where the "Invoice Check Grouping" field is not blank. (You can find additional interesting search criteria in the "Insert: Operators" drop down of the title bar.)
Now you may actually be looking to filter related records through a portal but, given that you've set up a self-join on the Invoice index on the Invoice table my guess is that, at best, this would show either 0 or 1 record for each Invoice record you display in your main layout.
To Filter Records with the "Portal Filter" method:
Let's assume, though, that you have a Client table where you'd like to see only the records with a non-blank "Invoice Check Grouping" value. The table set-up would be as follows:
Client
Client ID
[... other client info ...]
Invoice
Invoice ID
Client ID
Invoice Check Grouping
[... other invoice info ...]
With a relationship in the relationships graph:
Client::Client ID ------< Invoice::Client ID
From there you would set up a Form layout on the Client TO and create a portal showing records from the Invoice TO. From the options for the portal you would select "Filter Portal Records" and use a formula similar to:
not IsEmpty(Invoice::Invoice Check Grouping)
Finally, it's worth noting that a portal filter isn't appropriate for all display situations or calculations. You can set up a similar filter completely through your relationships graph (as I believe you have already tried to do.) This will work, once again, for viewing records through a portal but not for the records displayed by a layout itself.
The answers above don't actually help Ben with his question. They are workarounds.
I have the same problem as Ben, and I don't think there is a solution, even now in Filemaker 12. There is I think no way to define a relationship that will omit the related records where the match fields are empty.
Two options come to mind:
On a specific layout, you have more fine-grained control in the portal definition itself, and can use this to exclude the records
You can now use SQL queries to achieve this result within Filemkaer.