-
Re: Import Notes to Existing Leads
Balkar Singh Aug 21, 2017 5:49 AM (in response to Itay Billet)1 of 1 people found this helpfulIf you're importing the list, creating a separate custom field as a holder of new notes may make sense - and later, you can use the trigger Person is Created with the constraint of list import - and define Change Data Value as a flow step where you concatenate original notes with new notes by using concatenated tokens - {{Notesfield}}, {{Custom-Notesfield}}
Hope this helps,
Balkar
-
Re: Import Notes to Existing Leads
Dan Stevens. Aug 21, 2017 5:52 AM (in response to Itay Billet)To ensure fields that contain existing values don't get overwritten, your best approach is to create a custom "Notes History" field (field type: text). And then create a CDV flow step (with choice):
If NOTES is empty, NOTES-HISTORY = {{date/time}}: {{lead.NOTES}}
else
NOTES-HISTORY = {{date/time}}: {{lead.NOTES}}, {{lead.NOTES-HISTORY}}
-
Re: Import Notes to Existing Leads
Itay Billet Aug 21, 2017 6:55 AM (in response to Dan Stevens.)Thanks Dan, but I tried this and it doesn't seem to work. Does it work with data type "text" or only with "String"? (when adding the string field, the tokens are "auto-completed", it is not the case in text)
-
Re: Import Notes to Existing Leads
Dan Stevens. Aug 21, 2017 6:58 AM (in response to Itay Billet)Can you include screenshots of the smart campaign (smart list and flow) that is processing this upon import?
-
Re: Import Notes to Existing Leads
Itay Billet Aug 22, 2017 8:35 AM (in response to Dan Stevens.)Hi Dan, it was sorted out, I think I had I mis-typed the token name.
I'm trying to add a line break between the new notes and the old ones, is that possible?
-
Re: Import Notes to Existing Leads
Dan Stevens. Aug 22, 2017 9:17 AM (in response to Itay Billet)1 of 1 people found this helpfulWe use Sanford's approach here (don't be overwhelmed by the steps involved - as long as you follow them as outlined, it's very easy to implement): http://blog.teknkl.com/dark-mkto-alleys-line-break-token/
Also, rather than create a token in every program that needs this, just create it at the folder level so that all sub-folders/programs will inherit the token.
Once deployed, we use it as follows:
{{system.dateTime}}: {{trigger.Web Page}}{{my.line-break}}{{lead.Avanade Web Page History}}
-
Re: Import Notes to Existing Leads
Itay Billet Aug 23, 2017 7:12 AM (in response to Dan Stevens.)I followed the instructions and it worked, thanks!
-
-
-
-
-
-
Re: Import Notes to Existing Leads
Jazmine Moore Aug 21, 2017 9:13 AM (in response to Itay Billet)I would create a new custom field, as Balkar said, named something like "Notes Temp" (Text type). Import new notes into "Notes Temp" and then have a smart campaign that concatenates the "Notes Temp" and "Notes" together.
Smart list:
Trigger - Person is created
Trigger - Data Value Change > Attribute = "Notes Temp"; New Value = is not empty
Filter - Notes Temp is not empty
Flow:
Change Data Value > Attribute - Notes; New Value = {{system.date}}-{{lead.Notes Temp}} | {{lead.Notes}}