Difference Between Final And Last
Bernice Ebesugawa
Last activity date - notes_last_updated - The last time a note, call, email, meeting, or task was logged for a contact. This is set automatically by HubSpot based on user actions in the contact record.
Last contacted - notes_last_contacted - The last time a chat conversation, call, sales email, or meeting was logged for a contact. This is set automatically by HubSpot based on user actions in the contact record.
They are indeed very similar. The difference is limited to the fact that activity has a wider definition (including notes and tasks created on the contact record) that contact - when building workflows I think there are different potential uses cases for each piece of data. It is subtle though.
We have Zendesk integration (1-way sync) with Hubspot. When viewing a contact I see the Zendesk tickets logged as "integration" > "Zendesk"
When I look in the overview for the same contact it shows no recent communication. Is there a way that we can count a Zendesk ticket as communication?
To Summarize what we are trying to do at a high level is run reports that report accurately. We communicate with our existing customer base primarily via Zendesk tickets and would like the reports to reflect that a contact has been contacted anytime we have interacted with the customer via a Zendesk ticket.
"Last Contacted Date" implies the Contact has been contacted Outbound (as opposted the contact has contacted us or replied).
While "chat conversation" is listed, it seems like the only one that wouldn't be an "OUTBOUND" touch. So I
I ask because I'm working to build automation around the outbound work our sales team does to make property updates. We can't trigger workflows off of activity (oof), so I have to make due with contact level fields. So seeing if 'last contacted date' might suffice as an outbound-activity indicator.
Hi Got the difference between those two properties. If I am looking at the dates, there are activity dates, last contacted and engagement dates - what's the difference between the first two contact activity dates and engagement dates?
My understanding is that last activity date is the last date and time of a note, call, sales email, meeting, task, or chat by someone in your organization. Last contacted is the last date of a chat conversation, call, email, or meeting logged by someone in your organization (so no notes or tasks are logged here). And last engagement date is the last date of one-to-one email opens and clicks, lead revisits, meeting bookings, and form submissions by someone outside your organization.
What I like to do, without looping, is get the difference of the last and first temporal order of each of the unique x sample. For example, 367 should be 1.73. I tried using dplyr with lag but I can't seem to figure out how to make sure that difference is only between last and first.
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
If the message is the difference between numbers, then just show the difference and leave the numbers to a backup document. I chose a diverging bar chart because it shows the differences either above or below the comparison value by using both sides of the axis. When the actual value is greater than the comparison value, the bar goes to the left of the axis. When the actual value is less than the comparison value, the bar goes to the right of the axis.
As you will see in the full video, I created the visual using a single graph instead of two graphs, have used labels creatively to make the text and axis lines line up properly, and added a callout to focus the attention of the audience. I have an article on creating a diverging bar chart using a stacked bar chart to have more control over the data label format and an article on using data labels instead of category labels when you need more control of the formatting.
When you want to communicate the difference between two values, just show the difference, not all the source values. Turn that difference into a visual by using a diverging bar chart that makes the differences easy to understand.
I don't understand the difference between break and last (flags of rewrite). The documentation is rather abstruse. I've tried to switch between the two in some of my configs, but I couldn't spot any difference in behavior. Can someone please explain these flags in more detail? Preferably with an example that shows different behavior when flipping one flag to another.
You may have different sets of rewrite rules for different locations. When rewrite module meets last, it stops processing the current set and the rewritten request is passed once again to find the appropriate location (and the new set of rewriting rules). If the rule ends with break, the rewriting also stops, but the rewritten request is not passed to another location.
That is, if there are two locations: loc1 and loc2, and there's a rewriting rule in loc1 that changes loc1 to loc2 AND ends with last, the request will be rewritten and passed to location loc2. If the rule ends with break, it will belong to location loc1.
(2)Get the end-of-month values
I want to get the difference between the value at the end of the month two months ago and the one of the last month. If there is no value at the end of the month (which is null-value), I want to get the value closest to the end of the month.
Let me show my expect value more with my sample data(02).
In regards to your first question, you said you did not get the expected value, so what did you get? Something that could impact the output you are receiving would be how you are displaying the calculated field. A calculation as simple as start_point - target_point should give you the result you want if it is displayed in a table with a row for each start_date, but would aggregate differently (sum or average) if displayed in a KPI.
I'm sort of new to coding in general, but I have started trying to use some arcade expressions in my web maps, currently I have a web map which has a date painted field for hydrants and with the arcade expression below I am using the current date and this field to provide a count of the years and days since a hydrant was last painted.
However, I was QC'ing the data and noticed that for hydrants painted after 2020, it is going to be a day short as 2020 was a leap year - if the web map persists beyond 2024, it will then start being 2 days short.
With my limited knowledge I believe that I need to use some type of when or if statement to be able to use 366 rather than 365 (in var d calculation) i'm just now sure how I would go about doing it - would anybody be able to provide some pointers?
When comparing the duration I'm getting from the above code its not quite the same as most online time duration calculators - actually short by 2 days -- is there something obvious that I missing here? (See attachment for context)
Good stuff, In my head it works conceptually, (let the datetime module do the work - I'm guessing that's what its based on??) A few If Elses for the formatting and should be good. I hope the concept kinda makes sense.
You checked the option "Include end date in calculation", which doesn't not make sense in your case. For example, if you calculate the difference between 1/1/2020 and 1/2/2020 with the option checked, it returns 2 even though it's only one day later.
I have an index where each document in the index provides the number of open items and the number of closed items. I'd like to build a visualization that shows if the team is catching up closing issues or, if at times, there are more open issues added than closed. The end result I'd like is two lines where the color changes depending on that factor (more closed issues than created, green, the reverse, red).
However, I think you can answer most of your question using any of the visualizations in Kibana. You won't get conditional coloring though. To do this, you need to translate your question into aggregations. It sounds like you are storing the count of issues, and you are looking for change in count, which is a "differences" function in Lens or a "derivative" function in other parts of Kibana. You also need to choose the metric that you are taking the differences of: you can use Sum or Last Value for your example.
Thank you, derivative is what I ended up doing. I've used two layers with open issues and closed issues and the two gives me an idea of how the team performs. I am not 100% sure that I've got what I want.
@snicoll If you're already configured your Derivative function then you have seen that the Derivative function requires a sub-aggregation. I was recommending Sum or Last Value as the sub-aggregation to choose.
I used Max and then derivative on max of closed (same for open). I don't understand how sum could be applicable to my case since each document stores that total of open (and closed) issues. Not the number of open/closed issues for that particular timestamp.
The main factor is the time interval. You can easily get multiple documents in the same date bucket, and using the Max function could give you incorrect results. Using Last Value (which is called Top Hits in Elasticsearch) will always guarantee that you are comparing a single document at a time. Using Sum will guarantee that you've considered all documents in the time range. In your case, it sounds like Last Value/Top Hits is the correct choice because you can guarantee only one document per metric.
I agree that it would be good to have conditional coloring at that level, but that's a long-term goal for Lens, not short term. We will support conditional coloring of tables in Lens soon, it's currently being developed.
4a15465005