Meeting Title: Luke Daque’s Zoom Meeting Date: 2025-03-24 Meeting participants: Luke Daque, Caio Velasco
WEBVTT
1 00:15:56.890 ⇒ 00:15:57.890 Luke Daque: Hello!
2 00:16:03.660 ⇒ 00:16:05.349 Luke Daque: Hello, Kyle! Can you hear me?
3 00:16:08.980 ⇒ 00:16:10.040 Caio Velasco: Can you hear me now?
4 00:16:10.750 ⇒ 00:16:12.940 Luke Daque: Oh, yeah, I can hear you cool.
5 00:16:14.460 ⇒ 00:16:15.290 Caio Velasco: Hello!
6 00:16:16.760 ⇒ 00:16:17.370 Caio Velasco: Yep.
7 00:16:17.370 ⇒ 00:16:18.060 Luke Daque: Can you hear me?
8 00:16:18.525 ⇒ 00:16:19.920 Caio Velasco: Yeah, they can
9 00:16:19.920 ⇒ 00:16:22.430 Luke Daque: I, okay, cool. Yeah, I can hear you
10 00:16:25.670 ⇒ 00:16:29.420 Luke Daque: nice. So yeah, so where were we at?
11 00:16:33.230 ⇒ 00:16:40.549 Luke Daque: Were you able to like? Take a look at the Amazon order status. If like, there’s something you can find there
12 00:16:41.670 ⇒ 00:16:48.259 Caio Velasco: Yes, I took a quick look, but then you can ask me other things which I also like to ask you.
13 00:16:48.590 ⇒ 00:16:52.559 Caio Velasco: so maybe they can briefly ask you that I think it’s easier.
14 00:16:53.610 ⇒ 00:16:54.570 Luke Daque: Okay. Sure.
15 00:16:55.470 ⇒ 00:17:08.610 Caio Velasco: For example. I have had an issue in ticket that I had to investigate. The difference between these 2 fields here. Don’t think they are here anymore, because I deleted them.
16 00:17:09.609 ⇒ 00:17:10.250 Caio Velasco: Okay.
17 00:17:11.490 ⇒ 00:17:13.729 Caio Velasco: But let me show you this, is it
18 00:17:14.450 ⇒ 00:17:15.230 Luke Daque: Yeah, sure.
19 00:17:31.310 ⇒ 00:17:36.679 Caio Velasco: So yeah, it was. It was deleted. So we had this total product cost column.
20 00:17:36.910 ⇒ 00:17:37.490 Caio Velasco: Yeah.
21 00:17:37.490 ⇒ 00:17:37.910 Luke Daque: Looks like
22 00:17:37.910 ⇒ 00:17:39.109 Caio Velasco: Storage or stable.
23 00:17:39.600 ⇒ 00:17:47.010 Caio Velasco: Then they asked me to investigate the difference between this one and this one.
24 00:17:48.431 ⇒ 00:17:56.929 Caio Velasco: They are the same. They do exactly the same thing the only difference that the
25 00:17:57.170 ⇒ 00:18:09.239 Caio Velasco: the Amazon order cte were initializing it as no, because at the end, what this final
26 00:18:09.890 ⇒ 00:18:16.199 Caio Velasco: model this is basically a union of between Amazon and shopify
27 00:18:17.060 ⇒ 00:18:17.870 Luke Daque: Right.
28 00:18:18.110 ⇒ 00:18:26.839 Caio Velasco: Right. So this one has logic for both cities, but the other one has just for one. So it was like useless
29 00:18:26.840 ⇒ 00:18:27.410 Luke Daque: I see.
30 00:18:29.110 ⇒ 00:18:32.740 Caio Velasco: So. Yes, I deleted them. But then, before
31 00:18:33.600 ⇒ 00:18:38.419 Caio Velasco: pushing the Pr. I also checked if there was any other stable downstream.
32 00:18:38.550 ⇒ 00:18:44.170 Caio Velasco: and then you turn told me to go on Snowflake
33 00:18:44.390 ⇒ 00:18:49.139 Caio Velasco: run this like thing that I had never done this for history.
34 00:18:49.260 ⇒ 00:18:49.935 Caio Velasco: So
35 00:18:51.270 ⇒ 00:18:52.790 Luke Daque: And
36 00:18:54.260 ⇒ 00:18:59.520 Caio Velasco: If I run this query to see what queries have been
37 00:19:00.245 ⇒ 00:19:08.180 Caio Velasco: run against Snowflake that uses this column, I don’t get basically anything.
38 00:19:08.876 ⇒ 00:19:12.909 Caio Velasco: I just get my own query that I just run right now.
39 00:19:15.450 ⇒ 00:19:19.669 Caio Velasco: And then I was talking with you some in the test to show you.
40 00:19:20.570 ⇒ 00:19:21.203 Caio Velasco: Do you
41 00:19:22.370 ⇒ 00:19:22.960 Luke Daque: Jeez
42 00:19:26.270 ⇒ 00:19:39.280 Caio Velasco: Started more or less when the Pr. Didn’t work, because the Pr. Mentioned that there are other models using it. Yes, there, there is other model using it. I remember that I saw on Github
43 00:19:40.830 ⇒ 00:19:43.820 Caio Velasco: And then I was asked if I had to eliminate them or not.
44 00:19:44.570 ⇒ 00:19:48.340 Caio Velasco: and then I don’t know why, but
45 00:19:48.860 ⇒ 00:19:51.870 Caio Velasco: previously today, in the morning like 24th
46 00:19:52.796 ⇒ 00:19:55.529 Caio Velasco: I saw the Meta base
47 00:19:55.955 ⇒ 00:20:00.229 Caio Velasco: which I don’t know why it it appears here like I don’t know. It’s
48 00:20:00.740 ⇒ 00:20:08.489 Caio Velasco: I don’t know, if you know, this would be already a 1st question like, I know, that is different from method base, like as as if some metric from
49 00:20:08.700 ⇒ 00:20:11.460 Caio Velasco: back to order line
50 00:20:13.020 ⇒ 00:20:20.520 Caio Velasco: use it. Either the total product cost or or this one. I remember that this one is
51 00:20:20.740 ⇒ 00:20:24.619 Caio Velasco: because I put like the the thing here, right? It’s also getting
52 00:20:24.620 ⇒ 00:20:25.360 Luke Daque: Right.
53 00:20:25.810 ⇒ 00:20:35.150 Caio Velasco: From other one. So probably not even those 2 are using exactly that total protocol. But let’s assuming they were.
54 00:20:35.640 ⇒ 00:20:40.019 Caio Velasco: Well, this thing here is like Meta Base doing something in Norfolk
55 00:20:41.100 ⇒ 00:20:43.409 Luke Daque: That’s a service user. So
56 00:20:44.273 ⇒ 00:20:51.219 Luke Daque: I believe that’s the service account that we are using for Meta base. So anytime
57 00:20:51.743 ⇒ 00:20:57.799 Luke Daque: data is being ingested from snowflake to make Meta base. It’s using that user basically
58 00:20:58.950 ⇒ 00:20:59.530 Caio Velasco: Okay.
59 00:20:59.960 ⇒ 00:21:02.410 Luke Daque: Because in order for us to connect to
60 00:21:02.730 ⇒ 00:21:09.900 Luke Daque: in order for metabase, to connect to snowflake, it needs a user. And yeah, so that’s why
61 00:21:10.180 ⇒ 00:21:12.760 Luke Daque: that service account was created. So
62 00:21:12.910 ⇒ 00:21:16.869 Luke Daque: we can use it to connect or log into snowflake. Basically
63 00:21:19.210 ⇒ 00:21:20.430 Caio Velasco: Okay, okay,
64 00:21:21.910 ⇒ 00:21:28.429 Caio Velasco: So let’s so we have a like a scheduler or something that
65 00:21:28.760 ⇒ 00:21:39.179 Caio Velasco: brings the data into snowfake. I’m sorry not into snowfake into method based, or is it if someone changes something in the dashboard that somehow it
66 00:21:39.460 ⇒ 00:21:42.200 Caio Velasco: tries to run against Snowflake again?
67 00:21:45.440 ⇒ 00:21:48.009 Luke Daque: Can can you say? What can you say that again? I don’t think
68 00:21:48.010 ⇒ 00:21:54.029 Caio Velasco: So, yeah, no problem. I’m just wondering, like, where is it for?
69 00:21:56.940 ⇒ 00:21:59.940 Caio Velasco: So the service user method base
70 00:22:02.220 ⇒ 00:22:08.029 Caio Velasco: this one. So when does actually this, what is the trigger for this? Is it when someone
71 00:22:08.400 ⇒ 00:22:14.890 Caio Velasco: changes something in the dashboard that it automatically automatically goes into snowflake? Or is it something else
72 00:22:14.890 ⇒ 00:22:17.159 Luke Daque: Yeah, that’s a good question. I think
73 00:22:17.330 ⇒ 00:22:19.469 Luke Daque: I think it’s either that or
74 00:22:19.680 ⇒ 00:22:23.209 Luke Daque: cause. I’m also not sure I don’t have access to metabase.
75 00:22:23.690 ⇒ 00:22:29.140 Luke Daque: But from what? From my experience like in local studio, for example.
76 00:22:29.896 ⇒ 00:22:33.823 Luke Daque: or like in real, for example, it’s anytime that
77 00:22:34.650 ⇒ 00:22:39.690 Luke Daque: if there’s a set time like a cron job or a a
78 00:22:41.760 ⇒ 00:22:48.650 Luke Daque: What do you call it like? If if it refreshes the data every 15 min, then it does that every 15 min.
79 00:22:49.479 ⇒ 00:22:59.839 Luke Daque: But I’m not sure how metabase does that. Maybe it’s also like, I I think I saw like some you can do a query in Meta base, right?
80 00:23:00.490 ⇒ 00:23:15.969 Luke Daque: Or maybe even save a table that is in query format in metabase. So if I think every time you do that like, if there’s a change in the dashboard, then you create that query, then that will also trigger the service account to
81 00:23:16.230 ⇒ 00:23:19.060 Luke Daque: query that in Snowflake basically
82 00:23:20.540 ⇒ 00:23:22.949 Caio Velasco: Okay, okay, okay, that would be.
83 00:23:23.260 ⇒ 00:23:28.389 Caio Velasco: I don’t wait to see, like a new query in the the query, histories. No place, right?
84 00:23:41.380 ⇒ 00:23:51.879 Caio Velasco: Yeah. This is where, like, I usually get lost is I would try to like find where that service user methods come from. Just so that I have a good understanding of what is happening.
85 00:23:52.500 ⇒ 00:23:53.370 Caio Velasco: Plans.
86 00:23:58.540 ⇒ 00:24:03.010 Caio Velasco: Yeah. So what what would you do here like in this case? Where?
87 00:24:04.520 ⇒ 00:24:09.069 Caio Velasco: Because I mean, if I if I, if I run all the query history like.
88 00:24:10.160 ⇒ 00:24:12.450 Caio Velasco: for example, like right now.
89 00:24:13.070 ⇒ 00:24:13.770 Luke Daque: Yeah.
90 00:24:16.400 ⇒ 00:24:17.600 Caio Velasco: Alright! Give me that!
91 00:24:18.240 ⇒ 00:24:18.930 Caio Velasco: Go through that
92 00:24:18.930 ⇒ 00:24:24.530 Luke Daque: What’s the goal here? Is it like in Meta Base to make sure that we are using the new
93 00:24:24.730 ⇒ 00:24:30.529 Luke Daque: total product cost, or the one that you did that was not deleted, is it? Is it something like that?
94 00:24:30.890 ⇒ 00:24:39.820 Caio Velasco: So the goal is that I have to delete total for the cost. So before the meeting, I have to make sure that no dashboard, no
95 00:24:40.120 ⇒ 00:24:42.040 Caio Velasco: service, nothing is using
96 00:24:42.040 ⇒ 00:24:42.800 Luke Daque: Yeah.
97 00:24:43.390 ⇒ 00:24:48.400 Caio Velasco: When I do this query, when I do this query like, there’s not
98 00:24:49.700 ⇒ 00:24:50.410 Luke Daque: Yeah.
99 00:24:53.080 ⇒ 00:24:54.010 Luke Daque: Then.
100 00:25:01.130 ⇒ 00:25:04.819 Caio Velasco: There’s only my own query that I just ran like 4 times now
101 00:25:05.670 ⇒ 00:25:11.740 Luke Daque: I see. Yeah, in that case. And I think we should be good, right? Because we’re not seeing the
102 00:25:12.190 ⇒ 00:25:14.160 Luke Daque: service account doing that.
103 00:25:15.460 ⇒ 00:25:19.739 Luke Daque: Yeah, it just means it’s not being used in the database. Basically, that’s correct.
104 00:25:21.160 ⇒ 00:25:28.230 Caio Velasco: Okay. So if this is true, and I go to, let’s see.
105 00:25:28.880 ⇒ 00:25:31.881 Caio Velasco: Think it’s easier to go straight in
106 00:25:36.280 ⇒ 00:25:41.350 Caio Velasco: here, this one. So this is how the Pr. Failed. Richard Smith
107 00:25:42.920 ⇒ 00:25:48.540 Luke Daque: That’s really so. That’s a different one. Or is it the
108 00:25:48.540 ⇒ 00:25:49.590 Caio Velasco: No, no, that was the
109 00:25:49.590 ⇒ 00:25:50.880 Luke Daque: Calls, either those
110 00:25:50.880 ⇒ 00:25:57.109 Caio Velasco: Yeah, that’s it for the total cost. Yes. And that was in the morning. So total cost appears in this table
111 00:25:58.700 ⇒ 00:26:03.420 Caio Velasco: disable in yeah, basically, those 2 things
112 00:26:04.000 ⇒ 00:26:05.450 Luke Daque: When this happens, that’s true.
113 00:26:05.932 ⇒ 00:26:07.380 Caio Velasco: Delete the group
114 00:26:09.020 ⇒ 00:26:09.730 Luke Daque: Well, it’s
115 00:26:09.730 ⇒ 00:26:10.350 Caio Velasco: Scratch.
116 00:26:10.350 ⇒ 00:26:23.620 Luke Daque: It depends on the call, like, if, since you mentioned that we’re deleting total product cost because we are using the other one, the cogs product cost or something, then we might also need to update the
117 00:26:24.560 ⇒ 00:26:31.359 Luke Daque: the total product cost in these March models to the new one, which is the cogs product cost or something.
118 00:26:31.990 ⇒ 00:26:39.549 Luke Daque: So if you go to. And yeah, if you go to the the Vs code in daily Kpi Ag
119 00:26:41.240 ⇒ 00:26:44.090 Luke Daque: and search for the total product cost
120 00:26:46.560 ⇒ 00:26:51.150 Luke Daque: alright. It looks like we’re also using cogs. Product cost right?
121 00:26:52.430 ⇒ 00:26:55.030 Caio Velasco: It could be. Let’s see books.
122 00:26:55.300 ⇒ 00:26:55.740 Luke Daque: Yeah.
123 00:26:55.740 ⇒ 00:26:57.810 Caio Velasco: Yes, it also is
124 00:26:57.810 ⇒ 00:27:01.840 Luke Daque: So, yeah, I think, yeah, did.
125 00:27:02.780 ⇒ 00:27:05.469 Luke Daque: Was this something that Payas already?
126 00:27:06.233 ⇒ 00:27:09.230 Luke Daque: Confirm that we’re not using supposed to be using
127 00:27:10.130 ⇒ 00:27:17.560 Caio Velasco: No you you cancel said, like, we don’t really need bias. Input. Then I don’t know why. But
128 00:27:18.140 ⇒ 00:27:18.880 Caio Velasco: yeah.
129 00:27:18.880 ⇒ 00:27:19.610 Luke Daque: Okay.
130 00:27:19.920 ⇒ 00:27:29.250 Luke Daque: yeah. In that case, you can just remove it. Or remove. Like all of the cogs relate total product cost related fields there, like from Row 68,
131 00:27:29.360 ⇒ 00:27:35.279 Luke Daque: the 67 to 74. Those are all total product cost related. So you can just remove all of those
132 00:27:36.250 ⇒ 00:27:40.522 Luke Daque: because we are already using. We already have that I
133 00:27:42.020 ⇒ 00:27:46.270 Luke Daque: in 76, I think, and below
134 00:27:47.650 ⇒ 00:27:49.840 Caio Velasco: Yeah. So this is where my
135 00:27:50.440 ⇒ 00:28:15.849 Caio Velasco: my questions come, and then, if I stop to like, learn, it takes a day. But then they don’t see that they coming in my end, you know. Because if I were to do this that you just mentioned, I I myself kai doing this would be. I have to 1st understand the full model, how it was built, what is doing like literally everything from scratch, so that I could have the how do you say the
136 00:28:16.210 ⇒ 00:28:20.849 Caio Velasco: the the knowledge to to tell
137 00:28:21.130 ⇒ 00:28:27.379 Caio Velasco: you come, or whoever is reviewing that I remove it? This whole thing because it makes sense.
138 00:28:27.760 ⇒ 00:28:30.060 Caio Velasco: but otherwise I cannot defend my argument.
139 00:28:31.210 ⇒ 00:28:42.429 Caio Velasco: you know, like, so that’s where it starts the trouble. And that’s why they said like, it’s been a lot of time, but that’s why it’s been a lot of time, because I cannot just remove this like comment out right
140 00:28:44.410 ⇒ 00:28:45.320 Luke Daque: Yeah, you can.
141 00:28:45.470 ⇒ 00:28:51.540 Luke Daque: Well, you can easily defend that by like, since you already know.
142 00:28:52.890 ⇒ 00:28:54.280 Luke Daque: Wait, I think.
143 00:28:55.750 ⇒ 00:29:03.910 Luke Daque: Do you have the Dbt power user quick extension already installed
144 00:29:03.910 ⇒ 00:29:05.140 Caio Velasco: You know. What is that?
145 00:29:06.515 ⇒ 00:29:13.020 Luke Daque: That way. You can like see the lineage of all the models. I think that’s that would help a lot.
146 00:29:13.580 ⇒ 00:29:14.130 Luke Daque: because
147 00:29:14.130 ⇒ 00:29:14.660 Caio Velasco: But I think
148 00:29:14.660 ⇒ 00:29:15.530 Luke Daque: Really
149 00:29:16.640 ⇒ 00:29:26.920 Luke Daque: like ideally, you didn’t create a Pr yet until, unless like you ran the Ran Dvt right? And then you would have seen, like the failed ones.
150 00:29:27.620 ⇒ 00:29:33.440 Luke Daque: or something failed models and then fix them. But
151 00:29:33.970 ⇒ 00:29:34.760 Caio Velasco: Okay.
152 00:29:35.120 ⇒ 00:29:36.440 Luke Daque: But yeah, like.
153 00:29:36.440 ⇒ 00:29:41.470 Caio Velasco: I just ran on that for those specific 2 models that I
154 00:29:41.770 ⇒ 00:29:48.380 Caio Velasco: delete the total project box. And for those 2 models it worked. But I didn’t run the whole dbt. Run
155 00:29:49.160 ⇒ 00:29:50.020 Caio Velasco: so that
156 00:29:50.020 ⇒ 00:29:50.650 Luke Daque: Maybe
157 00:29:50.650 ⇒ 00:29:52.090 Caio Velasco: When I make this change
158 00:29:52.770 ⇒ 00:29:59.330 Luke Daque: Maybe just the the those 2 models, and then any downstream models related to that.
159 00:30:00.070 ⇒ 00:30:03.730 Luke Daque: So when you do a Dbt run or Dbt build. You can just
160 00:30:06.040 ⇒ 00:30:17.180 Luke Daque: just put like Dbt build and then select the model name right? It’s like dash S, and then model name, and then put a plus sign. After that
161 00:30:17.300 ⇒ 00:30:20.990 Luke Daque: that way it would run all the models downstream
162 00:30:21.880 ⇒ 00:30:25.150 Caio Velasco: Okay, okay. I didn’t know. I’ll do that next time.
163 00:30:26.020 ⇒ 00:30:26.840 Caio Velasco: Okay.
164 00:30:26.840 ⇒ 00:30:27.829 Luke Daque: Yeah, no. Problem.
165 00:30:28.290 ⇒ 00:30:32.839 Caio Velasco: And okay. But in this case.
166 00:30:33.250 ⇒ 00:30:36.020 Caio Velasco: for example, since we we see that this.
167 00:30:36.200 ⇒ 00:30:41.190 Caio Velasco: all this aggregated tables are kind of usable for the part.
168 00:30:43.590 ⇒ 00:30:51.030 Caio Velasco: I mean, would this be a new whole ticket for for, like me to again investigate different
169 00:30:51.580 ⇒ 00:30:53.580 Caio Velasco: this one and this one? Then it would
170 00:30:53.580 ⇒ 00:30:54.770 Luke Daque: I don’t think so.
171 00:30:54.770 ⇒ 00:30:55.549 Caio Velasco: 2 days.
172 00:30:56.530 ⇒ 00:31:01.980 Luke Daque: Going to be in the same ticket because it’s the same concept. Basically, it’s just
173 00:31:02.640 ⇒ 00:31:08.210 Luke Daque: well, if you if you think about it, since the the total product cost that you removed was already
174 00:31:08.740 ⇒ 00:31:12.209 Luke Daque: a down, an upstream model for this one.
175 00:31:12.520 ⇒ 00:31:20.850 Luke Daque: For, like, if you look at the from statement for this specific cte, if you scroll down.
176 00:31:23.340 ⇒ 00:31:28.049 Luke Daque: they scroll down to look at the from part
177 00:31:28.770 ⇒ 00:31:39.529 Luke Daque: there. So it’s coming from fact orders. And so, since you already know that you remove the total product cost from fact orders, then, for sure, you have to remove it here as well
178 00:31:40.080 ⇒ 00:31:42.650 Luke Daque: right, because it doesn’t make sense that it’s still
179 00:31:42.900 ⇒ 00:31:45.219 Luke Daque: needs to be there because it’s already removed.
180 00:31:45.740 ⇒ 00:31:54.540 Luke Daque: So I guess that’s that’s the easiest like defense. Or like, yeah, that’s right, whatever question. Yeah, so that
181 00:31:54.540 ⇒ 00:31:55.090 Caio Velasco: A lad.
182 00:31:55.090 ⇒ 00:31:55.470 Luke Daque: So you can
183 00:31:55.470 ⇒ 00:31:58.530 Caio Velasco: Unless this, this would generate another
184 00:31:58.730 ⇒ 00:32:16.740 Caio Velasco: another review on your premise, right? Like maybe here people say like, Oh, no! Here it makes sense to use it. And then you have to go. In fact, orders, and then actually make total product, not make sense. I mean, this is just a hypothesis that I have to consider. But I understand your point. It makes total sense
185 00:32:17.820 ⇒ 00:32:23.810 Luke Daque: And maybe what happens there is like if you can see in Row 69, there’s a case when statement
186 00:32:25.000 ⇒ 00:32:30.379 Luke Daque: so basically, it’s new subscription up cogs or something.
187 00:32:30.560 ⇒ 00:32:35.070 Luke Daque: and I don’t think we have that in the next block of code.
188 00:32:36.080 ⇒ 00:32:36.650 Luke Daque: If you
189 00:32:36.650 ⇒ 00:32:37.120 Caio Velasco: Detroit.
190 00:32:37.120 ⇒ 00:32:46.580 Luke Daque: Take a look. Row 69. Yeah. It says it’s a case. Wednesday. If it’s like case when customer type is new and subscription orders falls.
191 00:32:46.790 ⇒ 00:32:53.100 Luke Daque: then total product cost, and then it’s it’s called a new subscription cogs, or something right
192 00:32:53.700 ⇒ 00:32:54.420 Caio Velasco: Yes.
193 00:32:55.330 ⇒ 00:33:01.540 Luke Daque: And if you, if you scroll down at the product cost cogs, we don’t have that. We don’t have new
194 00:33:01.890 ⇒ 00:33:04.320 Luke Daque: subscription cost there
195 00:33:05.820 ⇒ 00:33:06.699 Caio Velasco: So it also
196 00:33:06.700 ⇒ 00:33:07.390 Luke Daque: Hey, Nancy?
197 00:33:07.390 ⇒ 00:33:14.649 Luke Daque: That? Yeah, it. It also depends. If Meta base is using those like the new subs cost or the
198 00:33:15.150 ⇒ 00:33:22.390 Luke Daque: new non sub cost, then we might need to recreate that using the cogs product cost.
199 00:33:22.780 ⇒ 00:33:26.400 Luke Daque: But if not, then we can directly delete them.
200 00:33:27.420 ⇒ 00:33:28.709 Luke Daque: Do you get what I mean?
201 00:33:29.100 ⇒ 00:33:32.690 Caio Velasco: Yes, I do. But then this is also another
202 00:33:33.030 ⇒ 00:33:36.229 Caio Velasco: 2 2 tickets. Right? Let’s say
203 00:33:37.710 ⇒ 00:33:41.750 Luke Daque: Yeah, you can. You can. You can do it like that as well. It can be a sub ticket
204 00:33:42.000 ⇒ 00:33:42.710 Luke Daque: or
205 00:33:42.710 ⇒ 00:33:52.850 Caio Velasco: Yeah, I have to investigate using this one from, we can would basically do this right
206 00:33:55.530 ⇒ 00:34:00.639 Luke Daque: Yeah, yeah, you can do the same thing and then use that new subs codes. Yep.
207 00:34:02.830 ⇒ 00:34:05.700 Luke Daque: it looks like nobody is using it.
208 00:34:06.290 ⇒ 00:34:08.460 Luke Daque: What about the other one? The
209 00:34:08.780 ⇒ 00:34:11.599 Luke Daque: try the other stuff. New nonsense!
210 00:34:18.409 ⇒ 00:34:19.899 Caio Velasco: No one is even using
211 00:34:22.210 ⇒ 00:34:31.499 Luke Daque: Yeah, in that case, we can remove that, those, because I believe
212 00:34:31.719 ⇒ 00:34:35.420 Luke Daque: that exists also in the monthly Kpi ad.
213 00:34:38.370 ⇒ 00:34:40.659 Luke Daque: so we can easily remove those
214 00:34:43.849 ⇒ 00:34:49.329 Caio Velasco: Okay, cool. So yeah, that’s a good way to do things. I can just come here and let’s see.
215 00:34:49.879 ⇒ 00:34:51.529 Caio Velasco: why is everything too long?
216 00:34:52.399 ⇒ 00:34:58.899 Caio Velasco: But okay, okay, perfect. I think for this, I’m good to at least move forward to the next step.
217 00:35:01.169 ⇒ 00:35:05.199 Caio Velasco: So let me go backward to the to the other part.
218 00:35:07.369 ⇒ 00:35:08.489 Caio Velasco: Yeah, it’s not cool.
219 00:35:09.989 ⇒ 00:35:12.879 Caio Velasco: So yeah, they canceled orders.
220 00:35:13.129 ⇒ 00:35:16.119 Caio Velasco: And we greets or postpayment.
221 00:35:16.639 ⇒ 00:35:23.929 Caio Velasco: So what I did was, Yeah, I was actually
222 00:35:24.709 ⇒ 00:35:27.039 Caio Velasco: thinking a bit on it, and then
223 00:35:27.599 ⇒ 00:35:29.459 Caio Velasco: try to like at least update.
224 00:35:29.689 ⇒ 00:35:33.939 Caio Velasco: I mean, not now. But when I’m done I will update some questions to you.
225 00:35:34.930 ⇒ 00:35:39.419 Caio Velasco: For example? Well, this is the the question like this is an order, cancel
226 00:35:39.609 ⇒ 00:35:42.299 Caio Velasco: event, pre or post. Pre. Yes.
227 00:35:42.889 ⇒ 00:35:44.960 Luke Daque: And that’s a good question.
228 00:35:45.140 ⇒ 00:35:47.350 Luke Daque: So what I what we can.
229 00:35:47.500 ⇒ 00:35:52.249 Luke Daque: if if I were doing that, and since I know that
230 00:35:53.890 ⇒ 00:36:01.040 Luke Daque: oh, no, wait is, is Javi still using Fivetran for the data ingestion or no, not not anymore.
231 00:36:04.710 ⇒ 00:36:05.879 Caio Velasco: That would be a decision
232 00:36:05.880 ⇒ 00:36:06.760 Luke Daque: They were useful.
233 00:36:06.760 ⇒ 00:36:08.639 Caio Velasco: I I assume not.
234 00:36:10.150 ⇒ 00:36:11.050 Luke Daque: Yeah.
235 00:36:11.970 ⇒ 00:36:19.390 Caio Velasco: Because for gorgeous it was portable for recharge. It was portable for shopify. It’s for
236 00:36:21.910 ⇒ 00:36:25.600 Luke Daque: We can always check by going to 5, 10.
237 00:36:26.450 ⇒ 00:36:28.010 Luke Daque: Try checking
238 00:36:39.540 ⇒ 00:36:40.120 Caio Velasco: Book.
239 00:36:45.580 ⇒ 00:36:46.509 Luke Daque: Wait a minute.
240 00:36:47.120 ⇒ 00:36:53.509 Luke Daque: But what we can do for this one is to try to look for
241 00:36:54.610 ⇒ 00:37:02.419 Luke Daque: in the fact orders table, since we know that the cancelled order is most probably in the fact. Orders table
242 00:37:04.590 ⇒ 00:37:11.450 Luke Daque: we can check like any kind of order status.
243 00:37:12.320 ⇒ 00:37:18.040 Luke Daque: That’s in the fact. Orders or fact, order lines table, and then
244 00:37:18.860 ⇒ 00:37:21.250 Caio Velasco: My bad. I think I lost you for a bit.
245 00:37:21.630 ⇒ 00:37:22.689 Caio Velasco: What did you say
246 00:37:24.280 ⇒ 00:37:29.200 Luke Daque: Oh, wait! This is shopify right or Amazon
247 00:37:31.980 ⇒ 00:37:35.740 Caio Velasco: I I believe it’s Amazon, because all the tickets are related to Amazon.
248 00:37:38.040 ⇒ 00:37:38.900 Luke Daque: What is that?
249 00:37:41.180 ⇒ 00:37:46.380 Caio Velasco: I said that it’s probably Amazon, because all tickets are related to Amazon. Dashboard.
250 00:37:47.580 ⇒ 00:37:54.929 Luke Daque: Oh, okay, in that case, maybe we can look at the Amazon orders.
251 00:37:55.860 ⇒ 00:37:58.920 Luke Daque: Not sure if that was an intermediate model or
252 00:38:01.010 ⇒ 00:38:02.280 Caio Velasco: In here.
253 00:38:05.130 ⇒ 00:38:05.930 Luke Daque: Yeah.
254 00:38:07.730 ⇒ 00:38:14.050 Luke Daque: So if we go to intermediate Amazon order.
255 00:38:15.880 ⇒ 00:38:25.409 Luke Daque: Hmm, yeah, that’s looks like it’s coming from order. Can you try to search for status order status.
256 00:38:26.440 ⇒ 00:38:31.089 Luke Daque: If there’s any field, there’s order status
257 00:38:34.370 ⇒ 00:38:36.960 Caio Velasco: We wanna see if there’s something on the 5 strength
258 00:38:37.820 ⇒ 00:38:44.090 Luke Daque: I don’t think you can see anything from 5 trend because we are using source there.
259 00:38:46.590 ⇒ 00:38:48.480 Luke Daque: how we are using the the
260 00:38:49.910 ⇒ 00:38:54.050 Luke Daque: yeah. If you look at the reference, it’s referencing the order line
261 00:38:54.280 ⇒ 00:38:59.018 Caio Velasco: But if you scroll down, this is our deadline.
262 00:38:59.830 ⇒ 00:39:03.950 Luke Daque: And coming from source already.
263 00:39:09.720 ⇒ 00:39:10.250 Luke Daque: Yep.
264 00:39:13.110 ⇒ 00:39:17.880 Caio Velasco: Esh is this one? Then I’m not sure if it’s 5 term or not.
265 00:39:19.640 ⇒ 00:39:23.240 Luke Daque: Can you click on that one and let’s check us.
266 00:39:23.620 ⇒ 00:39:26.490 Luke Daque: A table, maybe orders table.
267 00:39:27.900 ⇒ 00:39:34.006 Luke Daque: We should be able to know if it’s Fivetran. If it has a 5 tran field, 5 trends
268 00:39:35.720 ⇒ 00:39:37.290 Caio Velasco: Problem. Lastly.
269 00:39:37.290 ⇒ 00:39:39.640 Luke Daque: Yeah, like scroll down.
270 00:39:41.560 ⇒ 00:39:43.320 Luke Daque: Likely at the at the last
271 00:39:43.500 ⇒ 00:39:45.650 Luke Daque: the very last column would be.
272 00:39:45.830 ⇒ 00:39:47.520 Luke Daque: I don’t see his presence
273 00:39:47.520 ⇒ 00:39:52.520 Luke Daque: so. Yep. 5 grand sync. So it looks like it is coming from 5 grand
274 00:39:53.990 ⇒ 00:39:54.580 Caio Velasco: Do that
275 00:39:54.580 ⇒ 00:39:58.670 Luke Daque: Because one thing that 5 Tran has is an Erd
276 00:40:04.400 ⇒ 00:40:11.720 Luke Daque: if you search Google 5, grand Amazon. ERD,
277 00:40:15.300 ⇒ 00:40:16.920 Luke Daque: it’s like, Amazon.
278 00:40:19.010 ⇒ 00:40:19.820 Luke Daque: Yeah.
279 00:40:21.090 ⇒ 00:40:24.330 Luke Daque: Yeah. And if you click that, the 1st one.
280 00:40:25.650 ⇒ 00:40:33.629 Luke Daque: and if you scroll down there should be a ERD, like a
281 00:40:37.260 ⇒ 00:40:40.980 Luke Daque: yeah, that that one. Yeah, if you click on that one
282 00:40:42.350 ⇒ 00:40:48.919 Caio Velasco: Okay? So that’s what I was asking before in the like, there is documentation about it. Then
283 00:40:49.500 ⇒ 00:40:59.660 Luke Daque: Yeah, if it’s coming from 5 grand. So we’ll have to look for the orders. There’s a lot of pages. So maybe one of the that page is mostly for vendor
284 00:41:00.080 ⇒ 00:41:04.329 Luke Daque: stuff. So maybe there’s another page for order. Stuff
285 00:41:05.340 ⇒ 00:41:10.789 Luke Daque: the shipping order order. Item, is there orders, is there? So
286 00:41:12.180 ⇒ 00:41:16.269 Luke Daque: yeah, we should be able to see some something related to status.
287 00:41:19.780 ⇒ 00:41:25.059 Luke Daque: What was the question? Again, if Stat, if cancel status is post or
288 00:41:26.580 ⇒ 00:41:28.260 Caio Velasco: Yeah, if, what’s the
289 00:41:28.260 ⇒ 00:41:28.860 Luke Daque: What state.
290 00:41:28.860 ⇒ 00:41:31.410 Caio Velasco: I don’t know what they mean by stage backstage.
291 00:41:31.410 ⇒ 00:41:32.110 Luke Daque: I guess the state
292 00:41:32.110 ⇒ 00:41:32.500 Caio Velasco: Ages.
293 00:41:32.500 ⇒ 00:41:36.139 Luke Daque: If it’s before or after payment.
294 00:41:36.690 ⇒ 00:41:38.190 Caio Velasco: Going on this.
295 00:41:39.070 ⇒ 00:41:47.089 Caio Velasco: Okay? Because here I was exactly asking. I mean, I would go send this if there’s a cashier.
296 00:41:47.240 ⇒ 00:41:50.010 Caio Velasco: But the 1st question that I had was exactly like.
297 00:41:50.600 ⇒ 00:41:58.170 Caio Velasco: how do I know what is free or post, or who answered this question like it shouldn’t be the client who is using.
298 00:41:58.600 ⇒ 00:42:02.069 Caio Velasco: And otherwise, how can they know how, if they’re using correctly or not?
299 00:42:04.570 ⇒ 00:42:11.170 Luke Daque: Yeah, yeah, that’s actually, well, that’s a tricky question. Actually, like.
300 00:42:13.250 ⇒ 00:42:23.180 Caio Velasco: There is prepayment. Cancellation, which I assume is like. The order was placed, but payment was not captured.
301 00:42:24.690 ⇒ 00:42:32.720 Caio Velasco: probably like 3 payments cancellation, who cancel the 4 payments.
302 00:42:34.800 ⇒ 00:42:39.390 Caio Velasco: I mean, it’s not that this is before payment. There was a payment, but it was not captive
303 00:42:40.040 ⇒ 00:42:44.309 Caio Velasco: by the pos machine or by whatever, like the Payment gateway
304 00:42:44.990 ⇒ 00:42:47.430 Luke Daque: Could be both right. Because maybe
305 00:42:50.000 ⇒ 00:42:52.419 Luke Daque: and that’s what we need to like. Figure out.
306 00:42:52.990 ⇒ 00:42:57.679 Luke Daque: Cause like could be both. It could be like a an or a a.
307 00:43:00.740 ⇒ 00:43:07.129 Luke Daque: A customer, placed an order in Amazon, and then just canceled it.
308 00:43:07.410 ⇒ 00:43:09.850 Luke Daque: even if they did not pay yet.
309 00:43:11.140 ⇒ 00:43:20.110 Luke Daque: or it could be, they already sent a payment, and then they cancel the order. So in that case there would be a refund or something right
310 00:43:22.060 ⇒ 00:43:25.829 Caio Velasco: Yes, there would be a refund, for that would be the idea.
311 00:43:26.710 ⇒ 00:43:29.829 Caio Velasco: And you are assuming that is, in the order status.
312 00:43:30.260 ⇒ 00:43:30.810 Caio Velasco: Probably
313 00:43:35.710 ⇒ 00:43:38.969 Luke Daque: It can be in the order status, or maybe
314 00:43:39.710 ⇒ 00:43:43.859 Luke Daque: like in the order item, there is no status. There’s no order status.
315 00:43:44.490 ⇒ 00:43:49.490 Luke Daque: so it’s most likely the order status that gets canceled.
316 00:43:51.060 ⇒ 00:43:58.350 Luke Daque: So maybe what we can 2 is to query any order that has.
317 00:43:59.480 ⇒ 00:44:03.192 Luke Daque: Oh, well, well, first, st we need to know what are the statuses of the order.
318 00:44:04.490 ⇒ 00:44:10.500 Luke Daque: So so we’ll know if there is a status for cancelled orders. Basically
319 00:44:11.400 ⇒ 00:44:17.959 Caio Velasco: I believe so, because I remember seeing like when they are doing the Amazon CPU.
320 00:44:18.570 ⇒ 00:44:23.340 Caio Velasco: In the end there is both this.
321 00:44:23.640 ⇒ 00:44:25.920 Caio Velasco: Oh, we can check with, just so that we might
322 00:44:33.190 ⇒ 00:44:33.880 Luke Daque: Hey?
323 00:44:35.570 ⇒ 00:44:42.039 Luke Daque: So it looks like there is even a we even filtered there. That’s not canceled.
324 00:44:42.720 ⇒ 00:44:44.710 Luke Daque: Yeah, you can do that.
325 00:44:47.130 ⇒ 00:44:49.640 Caio Velasco: Directly from the source or compact orders.
326 00:44:50.080 ⇒ 00:44:53.940 Luke Daque: I would. Yeah, we can. Let’s do from source or no.
327 00:44:57.720 ⇒ 00:44:58.380 Caio Velasco: Or.
328 00:45:05.130 ⇒ 00:45:07.120 Caio Velasco: yeah, there is a canceled.
329 00:45:08.470 ⇒ 00:45:12.280 Caio Velasco: It’s okay. It’s not a lot of information, but that this is something
330 00:45:13.220 ⇒ 00:45:14.990 Luke Daque: So this is canceled.
331 00:45:15.380 ⇒ 00:45:19.810 Luke Daque: So next thing we need to know if the cancelled orders are
332 00:45:20.870 ⇒ 00:45:29.740 Luke Daque: before or after the payment. So we need to see if there’s any table related to payment in
333 00:45:31.400 ⇒ 00:45:35.150 Luke Daque: in the role, or like, yeah, so
334 00:45:35.770 ⇒ 00:45:39.610 Luke Daque: it might not be in the order. Maybe it’s in
335 00:45:42.690 ⇒ 00:45:48.779 Caio Velasco: From your questions. Do you believe there would be an it for a payment table foreign Key?
336 00:45:49.900 ⇒ 00:45:52.439 Luke Daque: Yeah, maybe there’s a payments table.
337 00:45:53.090 ⇒ 00:45:55.190 Luke Daque: I’m Amazon.
338 00:45:59.340 ⇒ 00:46:01.619 Luke Daque: There’s payment method
339 00:46:02.010 ⇒ 00:46:04.550 Caio Velasco: Let me see in the 1st time
340 00:46:04.550 ⇒ 00:46:11.920 Luke Daque: Yeah, can you check in the orders and then select all.
341 00:46:12.150 ⇒ 00:46:17.820 Luke Daque: Let’s let’s look for the payment method where order status is cancelled.
342 00:46:18.330 ⇒ 00:46:21.210 Luke Daque: Let’s check. What are the payment methods available?
343 00:46:31.240 ⇒ 00:46:32.170 Luke Daque: Maybe.
344 00:46:32.350 ⇒ 00:46:36.610 Luke Daque: Is there a payment status or the everything’s other at this moment?
345 00:46:38.630 ⇒ 00:46:40.980 Luke Daque: Is there a payment status in order
346 00:46:40.980 ⇒ 00:46:43.620 Caio Velasco: There’s billing stops
347 00:47:02.370 ⇒ 00:47:05.480 Caio Velasco: and solve this
348 00:47:10.570 ⇒ 00:47:14.789 Caio Velasco: under. Yeah, even for the whole table. There is just no. And all the
349 00:47:15.430 ⇒ 00:47:18.620 Luke Daque: Yeah, yeah, no worries.
350 00:47:21.870 ⇒ 00:47:29.190 Luke Daque: In that case, can we? Can we check the tables in Snowflake for Amazon?
351 00:47:29.560 ⇒ 00:47:33.590 Luke Daque: So we can see if there’s anything related to payments
352 00:47:36.230 ⇒ 00:47:37.150 Caio Velasco: Which ones
353 00:47:40.220 ⇒ 00:47:44.550 Luke Daque: In the raw Amazon data set or database
354 00:47:45.330 ⇒ 00:47:50.489 Luke Daque: can we check if there’s any any table that’s related to payments
355 00:47:51.700 ⇒ 00:47:54.400 Caio Velasco: In this one demonstrate other parts of it.
356 00:47:54.400 ⇒ 00:47:55.150 Luke Daque: Yes.
357 00:47:57.160 ⇒ 00:48:03.209 Luke Daque: So maybe. Well, there’s financial fulfillment
358 00:48:08.960 ⇒ 00:48:18.160 Luke Daque: what is fulfillment order can you click on fulfillment order, let’s just check what the fields are.
359 00:48:19.387 ⇒ 00:48:23.429 Luke Daque: It’s this address, I think. Looks like this is like 4.
360 00:48:24.130 ⇒ 00:48:25.210 Luke Daque: She shouldn’t
361 00:48:25.350 ⇒ 00:48:26.770 Caio Velasco: Shipments, here.
362 00:48:28.830 ⇒ 00:48:34.260 Luke Daque: So maybe there’s also payment related
363 00:48:36.000 ⇒ 00:48:37.040 Caio Velasco: This was 2 months
364 00:48:37.040 ⇒ 00:48:37.930 Luke Daque: Listen.
365 00:48:41.270 ⇒ 00:48:43.269 Caio Velasco: Maybe here, method.
366 00:48:44.990 ⇒ 00:48:46.580 Luke Daque: Yeah, let’s try.
367 00:48:47.350 ⇒ 00:48:50.520 Luke Daque: Let’s start to query that and see if there’s
368 00:48:59.190 ⇒ 00:49:01.209 Luke Daque: let’s try to query the methods.
369 00:49:01.370 ⇒ 00:49:03.550 Luke Daque: but doesn’t say status at all right.
370 00:49:04.790 ⇒ 00:49:06.960 Caio Velasco: Only methods. Yes.
371 00:49:07.160 ⇒ 00:49:07.970 Luke Daque: Yeah.
372 00:49:11.440 ⇒ 00:49:15.000 Luke Daque: it would be would have been great if there’s a status.
373 00:49:19.840 ⇒ 00:49:21.889 Luke Daque: No, it doesn’t have status
374 00:49:39.520 ⇒ 00:49:41.020 Caio Velasco: Standard and new ones.
375 00:49:49.500 ⇒ 00:49:50.529 Caio Velasco: Oh, it’s weird
376 00:49:58.530 ⇒ 00:49:59.310 Luke Daque: Let’s see.
377 00:50:01.980 ⇒ 00:50:03.110 Caio Velasco: Interesting
378 00:50:10.731 ⇒ 00:50:15.066 Caio Velasco: digital subscribe, and say they were talking about
379 00:50:20.410 ⇒ 00:50:25.490 Luke Daque: Anything else that can potentially be payment here.
380 00:50:26.330 ⇒ 00:50:30.210 Luke Daque: I’m also trying to look at the Erd right now from
381 00:50:30.880 ⇒ 00:50:31.360 Caio Velasco: Okay.
382 00:50:31.360 ⇒ 00:50:32.950 Luke Daque: And maybe
383 00:50:32.950 ⇒ 00:50:41.989 Caio Velasco: When you have this this type of question, do you usually query the information schema to try to like? See if there’s any column in the poll.
384 00:50:42.090 ⇒ 00:50:44.810 Caio Velasco: It’s no flick, or you don’t know that
385 00:50:47.420 ⇒ 00:50:55.100 Luke Daque: Oh, I don’t think so. I mean, yeah, I don’t.
386 00:50:55.310 ⇒ 00:50:57.329 Luke Daque: I don’t think I’d do that
387 00:50:57.620 ⇒ 00:50:58.200 Caio Velasco: Oops!
388 00:50:58.200 ⇒ 00:51:01.560 Luke Daque: Just from I don’t know what’s the best way, though it’s just like
389 00:51:02.680 ⇒ 00:51:03.550 Caio Velasco: That’s true like that
390 00:51:03.550 ⇒ 00:51:05.000 Luke Daque: Trying. Yeah.
391 00:51:07.220 ⇒ 00:51:09.449 Caio Velasco: If it’s too noisy for you, let me know.
392 00:51:09.590 ⇒ 00:51:13.610 Caio Velasco: because I mean like there’s always a lot of space
393 00:51:14.605 ⇒ 00:51:15.100 Luke Daque: Yeah.
394 00:51:29.360 ⇒ 00:51:33.030 Caio Velasco: So we wanna find basically anything related to payments.
395 00:51:33.820 ⇒ 00:51:41.569 Caio Velasco: or even 3 or 4 payments, or 3 or post is decided by we trying to find.
396 00:51:41.840 ⇒ 00:51:49.449 Caio Velasco: And the how can I see like a cancellation after our order was I? I don’t
397 00:51:49.450 ⇒ 00:51:49.840 Luke Daque: Yeah.
398 00:51:49.840 ⇒ 00:51:52.099 Caio Velasco: We just yeah, no idea.
399 00:51:52.760 ⇒ 00:51:58.769 Luke Daque: Well, what I was thinking is like, if there was a payment method table, and then we can
400 00:51:59.060 ⇒ 00:52:02.760 Luke Daque: query and order id from that payment table.
401 00:52:03.470 ⇒ 00:52:09.810 Luke Daque: and and we see a payment status. So we’ll just query any cancelled order
402 00:52:11.490 ⇒ 00:52:16.090 Luke Daque: like even all canceled orders there order ids, and then we’ll be able to know
403 00:52:16.250 ⇒ 00:52:19.270 Luke Daque: whether the payment has pushed through or not.
404 00:52:19.390 ⇒ 00:52:23.769 Luke Daque: Right cause. If if it pushed through, then it means that the canceled are
405 00:52:24.580 ⇒ 00:52:29.249 Luke Daque: post payment, meaning after payment. But if there are no none
406 00:52:29.420 ⇒ 00:52:38.240 Luke Daque: like all of the order, cancelled, orders don’t have payment statuses, then that means they are 3 payment right?
407 00:52:38.340 ⇒ 00:52:41.929 Luke Daque: But if they’re both, then that could mean
408 00:52:42.290 ⇒ 00:52:44.629 Luke Daque: it depends like it can be both.
409 00:52:44.770 ⇒ 00:52:51.919 Luke Daque: There are cancelled orders that are prepayment. There are cancelled orders that are post payment. Something like that is like where my
410 00:52:53.380 ⇒ 00:52:54.540 Luke Daque: faults are.
411 00:52:56.310 ⇒ 00:52:56.910 Luke Daque: Name it
412 00:52:56.910 ⇒ 00:52:57.229 Caio Velasco: There we go!
413 00:52:57.230 ⇒ 00:53:00.589 Luke Daque: This one financial stuff, financial tables.
414 00:53:03.620 ⇒ 00:53:05.139 Caio Velasco: Yeah, I’m trying to make the
415 00:53:05.660 ⇒ 00:53:09.579 Caio Velasco: check also on our trend. Erd for payment
416 00:53:10.410 ⇒ 00:53:10.800 Luke Daque: Yeah.
417 00:53:10.800 ⇒ 00:53:18.349 Caio Velasco: There are things but bearing, though I’m gonna
418 00:53:19.120 ⇒ 00:53:19.830 Luke Daque: Yes.
419 00:53:21.280 ⇒ 00:53:23.170 Caio Velasco: Try to do a 1 by one
420 00:53:34.420 ⇒ 00:53:35.760 Luke Daque: Status.
421 00:53:37.060 ⇒ 00:53:39.900 Luke Daque: There’s invoice status.
422 00:53:41.210 ⇒ 00:53:43.420 Luke Daque: But this doesn’t mean paid right.
423 00:53:43.870 ⇒ 00:53:45.700 Luke Daque: It’s just invoiced.
424 00:53:47.970 ⇒ 00:53:48.680 Luke Daque: Hmm.
425 00:53:52.500 ⇒ 00:53:57.260 Luke Daque: and send shit instead.
426 00:54:03.350 ⇒ 00:54:05.580 Luke Daque: Item, offer summary
427 00:54:12.160 ⇒ 00:54:15.620 Caio Velasco: Then there is this one quads quad. Famous is it
428 00:54:20.500 ⇒ 00:54:25.660 Luke Daque: Tracking. Summary status point transfer.
429 00:54:27.560 ⇒ 00:54:28.600 Luke Daque: Start this.
430 00:54:30.500 ⇒ 00:54:31.180 Luke Daque: Okay.
431 00:54:54.110 ⇒ 00:54:55.030 Caio Velasco: Department.
432 00:55:00.190 ⇒ 00:55:00.880 Caio Velasco: There you go.
433 00:55:09.010 ⇒ 00:55:10.090 Caio Velasco: I agree.
434 00:55:11.670 ⇒ 00:55:12.370 Caio Velasco: One
435 00:55:26.850 ⇒ 00:55:32.920 Luke Daque: I wonder if that’s in Amazon documentation anywhere?
436 00:55:41.190 ⇒ 00:55:44.270 Luke Daque: Because I tried to just ask Chat Gpt about it.
437 00:55:44.270 ⇒ 00:55:47.869 Caio Velasco: Yeah, okay, I will, literally perfect.
438 00:55:48.270 ⇒ 00:55:54.160 Luke Daque: And it actually said, I can let me just
439 00:55:54.530 ⇒ 00:56:00.110 Luke Daque: share it in the in the chat. Then think it’s easier.
440 00:56:04.230 ⇒ 00:56:10.760 Luke Daque: That’s why I was like trying to see if there’s any documentation from Amazon about it.
441 00:56:11.110 ⇒ 00:56:15.230 Luke Daque: But Chat Gpt basically said it can be either way.
442 00:56:15.920 ⇒ 00:56:18.320 Luke Daque: It depends on when it was canceled.
443 00:56:19.770 ⇒ 00:56:28.339 Luke Daque: If it was canceled after the payment was processed, then it’s post payment. But if it was cancelled
444 00:56:29.010 ⇒ 00:56:34.480 Luke Daque: before it was shipped before the order was shipped, and it’s prepayment
445 00:56:53.890 ⇒ 00:56:54.910 Luke Daque: and
446 00:57:01.550 ⇒ 00:57:02.519 Caio Velasco: I do.
447 00:57:03.530 ⇒ 00:57:04.480 Caio Velasco: It is
448 00:57:10.160 ⇒ 00:57:11.220 Caio Velasco: good evening. Thanks.
449 00:57:17.640 ⇒ 00:57:23.089 Caio Velasco: but that’s the thing like I know that we have to like, try to look for things, but
450 00:57:23.470 ⇒ 00:57:30.330 Caio Velasco: only like even the financial table. Like, if we don’t have knowledge on, what is this?
451 00:57:31.482 ⇒ 00:57:41.419 Caio Velasco: We are looking for something without any any assumption and premise, I mean, can I? Financial shipping, direct payment? I don’t even know where that is.
452 00:57:41.890 ⇒ 00:57:54.690 Caio Velasco: Yeah. So that’s why that’s why it was taking me too long, because I was literally assuming that Robert, who is what the one responsible for the client, like product, owner, business analyst, analyst.
453 00:57:54.910 ⇒ 00:57:59.830 Caio Velasco: I thought that he would have these answers because it’s building the product with the client.
454 00:58:00.820 ⇒ 00:58:08.180 Caio Velasco: I just I didn’t know, because otherwise we can’t. We have no one to ask
455 00:58:09.280 ⇒ 00:58:12.470 Luke Daque: Yeah. And maybe even maybe this was
456 00:58:13.000 ⇒ 00:58:18.270 Luke Daque: Robert’s question. Maybe this is not the client’s question, right?
457 00:58:18.500 ⇒ 00:58:19.360 Luke Daque: And
458 00:58:20.280 ⇒ 00:58:26.930 Luke Daque: or yeah, maybe the client asked him, and maybe he also doesn’t know, and he’s trying to ask us for help to
459 00:58:27.830 ⇒ 00:58:29.809 Luke Daque: find out something like that.
460 00:58:29.810 ⇒ 00:58:30.979 Caio Velasco: Okay. Okay. Baby.
461 00:58:31.620 ⇒ 00:58:32.439 Luke Daque: But yeah.
462 00:58:32.440 ⇒ 00:58:37.429 Caio Velasco: Because when I was yeah, in my previous job, I was working more like as a Va. So on the client side.
463 00:58:37.580 ⇒ 00:58:47.009 Caio Velasco: whenever I were to take a question to the engineers. I had to 1st understand the whole product with the client, so that I can go to the engineers, explain everything.
464 00:58:47.400 ⇒ 00:58:50.019 Caio Velasco: and then ask them like a ticket
465 00:58:51.050 ⇒ 00:58:51.540 Luke Daque: Hmm.
466 00:58:51.540 ⇒ 00:58:54.029 Caio Velasco: Because otherwise we are always playing.
467 00:58:54.210 ⇒ 00:58:57.249 Caio Velasco: So that’s why I was assuming this. Because that’s what I used to do.
468 00:58:57.930 ⇒ 00:58:58.370 Luke Daque: Yeah.
469 00:58:58.370 ⇒ 00:59:00.449 Caio Velasco: Okay, I see that, does it work.
470 00:59:00.880 ⇒ 00:59:06.669 Caio Velasco: So now. But yeah, so like.
471 00:59:07.980 ⇒ 00:59:09.310 Luke Daque: It’s kind of tricky.
472 00:59:09.670 ⇒ 00:59:10.469 Luke Daque: Thank you.
473 00:59:11.530 ⇒ 00:59:19.570 Luke Daque: We cannot. We can spend hours for this like like looking at the data and trying to find out whether an order
474 00:59:20.340 ⇒ 00:59:24.880 Luke Daque: cancelled orders before or after payment. But yeah, that would
475 00:59:25.120 ⇒ 00:59:32.889 Luke Daque: entail us looking at the Erd from Amazon or looking at the tables from the role data sources to find out
476 00:59:33.190 ⇒ 00:59:36.740 Luke Daque: if we can do a query joining both payment and
477 00:59:37.510 ⇒ 00:59:45.370 Luke Daque: orders and stuff like that. Right? So we can have some something to show like data driven?
478 00:59:48.710 ⇒ 00:59:55.020 Luke Daque: Answer to the question, basically, yeah, maybe this one
479 00:59:56.080 ⇒ 01:00:00.249 Luke Daque: cod. Oh, this is cod payment execution
480 01:00:01.840 ⇒ 01:00:03.689 Caio Velasco: That’s the one that I tried to
481 01:00:09.380 ⇒ 01:00:14.119 Luke Daque: But this is for cod. It looks like cash on delivery, and I don’t think, like
482 01:00:14.800 ⇒ 01:00:22.260 Luke Daque: all orders are cash on delivery. So maybe there’s maybe just some so, and for sure.
483 01:00:22.260 ⇒ 01:00:26.020 Caio Velasco: See if we have this table, but I don’t think we have.
484 01:00:26.280 ⇒ 01:00:27.030 Caio Velasco: Hmm!
485 01:00:28.160 ⇒ 01:00:37.220 Luke Daque: Yeah, because I don’t think we also like loaded all tables from Amazon, because it would like entail cost as well
486 01:00:38.200 ⇒ 01:00:42.440 Luke Daque: like in 5 trend. We just loaded the tables that we need.
487 01:00:43.230 ⇒ 01:00:44.100 Luke Daque: That’s also like
488 01:00:44.100 ⇒ 01:00:45.350 Caio Velasco: Okay. I don’t know.
489 01:00:46.820 ⇒ 01:00:47.750 Luke Daque: Yeah.
490 01:00:49.015 ⇒ 01:00:59.040 Caio Velasco: I thought that was just like reconnecting into the clients and getting like from with that I don’t know login and getting everything.
491 01:00:59.640 ⇒ 01:01:04.110 Caio Velasco: And then, okay, so we could still have tables that were not even in desks.
492 01:01:04.440 ⇒ 01:01:09.880 Luke Daque: Yes, that’s correct. There, there’s we’re not ingesting everything at the moment, because it’s
493 01:01:10.260 ⇒ 01:01:13.399 Luke Daque: quite costly as well. Like 5 grand is like
494 01:01:16.470 ⇒ 01:01:24.549 Luke Daque: it. Their their price is like based on the number of rows ingested. So the more tables we are ingesting, the more rows we are
495 01:01:25.050 ⇒ 01:01:28.160 Luke Daque: getting billed at 4 or something.
496 01:01:28.350 ⇒ 01:01:33.870 Luke Daque: So if if it’s a table that we’re not using for anything, then there’s no use ingesting that table.
497 01:01:34.080 ⇒ 01:01:35.649 Luke Daque: Just gonna be cost.
498 01:01:40.840 ⇒ 01:01:44.439 Luke Daque: Oh, please look
499 01:01:44.440 ⇒ 01:01:45.980 Caio Velasco: Does this make any sense
500 01:01:46.410 ⇒ 01:01:47.959 Luke Daque: That’s that makes sense.
501 01:01:48.880 ⇒ 01:01:56.130 Luke Daque: Pending means an order is placed, but payment has not been authorized. Can you scroll down to see if there’s anything cancelled.
502 01:01:56.540 ⇒ 01:01:58.260 Luke Daque: canceled, only to be cancelled
503 01:02:07.960 ⇒ 01:02:14.149 Caio Velasco: So if the payment was authorized, we are in a host situation. If the payment yes, our
504 01:02:14.150 ⇒ 01:02:19.180 Caio Velasco: spending or pending availability, then we are in a free
505 01:02:20.070 ⇒ 01:02:20.620 Luke Daque: Yeah.
506 01:02:20.620 ⇒ 01:02:21.920 Caio Velasco: Payment, state
507 01:02:23.360 ⇒ 01:02:24.120 Luke Daque: That’s right.
508 01:02:24.120 ⇒ 01:02:27.940 Caio Velasco: Then they they want to know if in this 2 subsets
509 01:02:28.680 ⇒ 01:02:33.820 Caio Velasco: or universe they want to know if, either in free or false, there has.
510 01:02:34.330 ⇒ 01:02:35.969 Caio Velasco: There are canceled stuff
511 01:02:36.876 ⇒ 01:02:45.049 Caio Velasco: at the end of the day. Mathematically. We’re just looking at 3 subsets like before after and cancel. And we want to know the intersection
512 01:02:45.370 ⇒ 01:02:46.550 Caio Velasco: a problem, then
513 01:02:46.980 ⇒ 01:02:48.069 Luke Daque: Yeah, and then
514 01:02:48.460 ⇒ 01:02:49.120 Caio Velasco: Tomorrow’s.
515 01:02:49.120 ⇒ 01:02:51.810 Luke Daque: And then then, yeah, I think, yeah, I think it’s.
516 01:02:53.250 ⇒ 01:02:54.729 Luke Daque: And I think it’s the
517 01:02:59.240 ⇒ 01:03:06.630 Luke Daque: It’s a combination of both, like like there are canceled orders that are pre payment. And there are canceled orders that are post
518 01:03:07.200 ⇒ 01:03:17.679 Luke Daque: payment. But yeah, that’s that’s just my feeling. It’s not really an objective or like data based going pollution
519 01:03:28.430 ⇒ 01:03:30.320 Caio Velasco: You will best be as well
520 01:03:50.910 ⇒ 01:03:54.239 Luke Daque: I guess we can look at the fulfilled orders.
521 01:03:56.260 ⇒ 01:04:00.609 Luke Daque: Are there any fulfilled orders, table or fulfillment table
522 01:04:00.730 ⇒ 01:04:03.370 Luke Daque: that we can use in Snowflake?
523 01:04:05.880 ⇒ 01:04:09.650 Luke Daque: Can we look at the the snowflake? Draw
524 01:04:15.290 ⇒ 01:04:19.080 Caio Velasco: With the workforce
525 01:04:20.740 ⇒ 01:04:23.990 Luke Daque: Maybe in Snowflake. Let’s try. Let’s try to check
526 01:04:24.740 ⇒ 01:04:25.740 Caio Velasco: Okay, yeah, what about
527 01:04:25.740 ⇒ 01:04:29.960 Luke Daque: That one fulfillment order. Yeah, it has fulfillment action.
528 01:04:30.530 ⇒ 01:04:35.700 Luke Daque: If we have a fulfillment order. Yeah, let’s try to statement.
529 01:04:36.560 ⇒ 01:04:38.450 Luke Daque: Query canceled.
530 01:04:38.760 ⇒ 01:04:42.560 Luke Daque: Let’s try to query that table.
531 01:04:49.660 ⇒ 01:04:54.410 Luke Daque: and then put where where?
532 01:04:58.160 ⇒ 01:05:02.940 Luke Daque: where? Order? Id? Oh, yeah. Let’s let’s do that first.st
533 01:05:09.880 ⇒ 01:05:10.910 Luke Daque: Okay?
534 01:05:11.560 ⇒ 01:05:12.980 Luke Daque: And it has
535 01:05:24.710 ⇒ 01:05:26.220 Caio Velasco: Once I will record
536 01:05:27.510 ⇒ 01:05:28.240 Luke Daque: D
537 01:05:34.760 ⇒ 01:05:35.840 Caio Velasco: That’s it.
538 01:05:39.670 ⇒ 01:05:40.470 Luke Daque: Okay.
539 01:05:42.428 ⇒ 01:05:46.559 Caio Velasco: So there’s not related to payments here, or cancellation
540 01:05:46.960 ⇒ 01:05:51.410 Luke Daque: But yeah, yeah, but I think if it’s if it’s complete or like.
541 01:05:51.720 ⇒ 01:05:53.579 Luke Daque: if it if the order is shipped.
542 01:05:53.730 ⇒ 01:05:56.069 Luke Daque: then that means it already went from.
543 01:05:56.520 ⇒ 01:06:01.850 Luke Daque: It’s it was already will feel. I mean it was. The payment would have been
544 01:06:02.010 ⇒ 01:06:08.500 Luke Daque: invoiced already, or something right. It would have been paid already, unless it’s cod right?
545 01:06:08.500 ⇒ 01:06:10.529 Caio Velasco: And you read first, st and you return
546 01:06:11.080 ⇒ 01:06:17.280 Luke Daque: Can we filter all? Can we query all order, or cancelled orders in this table
547 01:06:17.810 ⇒ 01:06:25.360 Luke Daque: like instead of limit to let’s do where order id in.
548 01:06:26.240 ⇒ 01:06:33.730 Luke Daque: and then let’s do a sub query that’s like, select all or id from orders
549 01:06:43.310 ⇒ 01:06:45.420 Luke Daque: where status is canceled
550 01:06:56.630 ⇒ 01:06:57.759 Caio Velasco: From the order
551 01:07:00.050 ⇒ 01:07:01.660 Luke Daque: Yeah, maybe something. Like,
552 01:07:07.320 ⇒ 01:07:08.220 Caio Velasco: Your wife.
553 01:07:11.110 ⇒ 01:07:13.109 Caio Velasco: What are you trying to find here
554 01:07:15.230 ⇒ 01:07:17.007 Luke Daque: Something like, wait
555 01:07:18.900 ⇒ 01:07:20.679 Luke Daque: Where earlier I do.
556 01:07:21.540 ⇒ 01:07:22.350 Luke Daque: Hey?
557 01:07:23.770 ⇒ 01:07:27.670 Luke Daque: Is it called Id from?
558 01:07:44.000 ⇒ 01:07:46.209 Luke Daque: Maybe something might miss.
559 01:07:47.780 ⇒ 01:07:52.300 Luke Daque: I I see I sent it into slack, or maybe
560 01:08:01.530 ⇒ 01:08:02.899 Luke Daque: oh, yeah, I think I missed that
561 01:08:03.880 ⇒ 01:08:09.110 Luke Daque: in canceled I missed a quotation mark or something.
562 01:08:11.970 ⇒ 01:08:14.290 Luke Daque: The apostrophe here.
563 01:08:18.460 ⇒ 01:08:22.760 Luke Daque: Oh, wait! What Amazon setting partner
564 01:08:25.630 ⇒ 01:08:29.769 Caio Velasco: Maybe there’s no, I think it’s on my own order.
565 01:08:33.380 ⇒ 01:08:42.880 Luke Daque: Okay, let’s oh, the 1st one should not be orders. It should be the payment method, detail. Item, right? I mean the fulfillment something. What was that?
566 01:08:42.880 ⇒ 01:08:43.950 Caio Velasco: Oh!
567 01:08:47.560 ⇒ 01:08:50.470 Luke Daque: We’ll fill them in order instead of orders.
568 01:08:55.240 ⇒ 01:09:01.019 Caio Velasco: And in there is it id or seller, fulfillment, order, id right
569 01:09:04.060 ⇒ 01:09:07.460 Luke Daque: Yeah, it should be seller fulfilling board right?
570 01:09:08.439 ⇒ 01:09:13.729 Luke Daque: Or maybe this payable order. Id. I don’t know what’s the right one.
571 01:09:14.399 ⇒ 01:09:17.690 Luke Daque: Wait. Let’s check the Erd from 5 Tran
572 01:09:21.229 ⇒ 01:09:23.270 Luke Daque: fulfillment order
573 01:09:24.830 ⇒ 01:09:26.550 Caio Velasco: Seems to be this service
574 01:09:30.859 ⇒ 01:09:33.669 Luke Daque: Seller fulfilling that. Okay, let’s do that.
575 01:09:38.309 ⇒ 01:09:42.509 Luke Daque: Select where seller fulfillment idea like that
576 01:09:43.169 ⇒ 01:09:46.389 Luke Daque: and select. Is it Amazon order? Id?
577 01:09:46.749 ⇒ 01:09:49.389 Luke Daque: Oh, doesn’t look like there’s anything
578 01:09:54.000 ⇒ 01:09:57.800 Caio Velasco: Selected all the appropriate order. They were confused
579 01:09:58.090 ⇒ 01:10:03.600 Caio Velasco: but canceled, and it didn’t find anything which kind of date well, makes sense
580 01:10:03.600 ⇒ 01:10:10.879 Luke Daque: Can you, Re? Can you remove the where statement? In the where order status is cancelled, we should find something right.
581 01:10:11.150 ⇒ 01:10:15.290 Luke Daque: I mean, no, not not that part in the sub query
582 01:10:16.030 ⇒ 01:10:17.970 Luke Daque: at the right? Yeah, that one.
583 01:10:21.160 ⇒ 01:10:22.980 Luke Daque: Then close parenthesis.
584 01:10:26.580 ⇒ 01:10:29.030 Luke Daque: I think we need the close parenthesis.
585 01:10:33.240 ⇒ 01:10:34.030 Luke Daque: Yeah.
586 01:10:34.350 ⇒ 01:10:38.119 Luke Daque: See what it is that should show something right? Yeah.
587 01:10:38.830 ⇒ 01:10:44.529 Luke Daque: So it looks like, just based on that. If we filter
588 01:10:44.960 ⇒ 01:10:49.909 Luke Daque: the fulfillment order or just the orders that were cancelled there were none.
589 01:10:50.280 ⇒ 01:10:57.560 Luke Daque: So it’s most likely that all the cancelled orders were not fulfilled, which means
590 01:10:58.960 ⇒ 01:11:04.140 Luke Daque: which most possibly means that they are pre payment
591 01:11:07.830 ⇒ 01:11:10.130 Luke Daque: right, because based
592 01:11:10.130 ⇒ 01:11:10.590 Caio Velasco: Oh, yeah.
593 01:11:10.590 ⇒ 01:11:16.430 Luke Daque: The document that you looked at earlier in the orders. Api document.
594 01:11:19.040 ⇒ 01:11:20.230 Caio Velasco: Is that interesting?
595 01:11:21.020 ⇒ 01:11:22.010 Luke Daque: Well
596 01:11:28.732 ⇒ 01:11:36.990 Luke Daque: did it say? I don’t think it said like it only said pending and active pending, or something that are
597 01:11:40.100 ⇒ 01:11:41.949 Luke Daque: not authorized.
598 01:11:43.170 ⇒ 01:11:52.840 Luke Daque: There’s unshipped, unshipped means payment has been authorized, but no items have been shipped, partially shipped
599 01:11:57.340 ⇒ 01:12:04.050 Caio Velasco: Then also look for one second here, 63,
600 01:12:04.050 ⇒ 01:12:05.550 Luke Daque: And so
601 01:12:10.610 ⇒ 01:12:11.160 Caio Velasco: Good.
602 01:12:21.680 ⇒ 01:12:22.450 Luke Daque: Okay.
603 01:12:32.630 ⇒ 01:12:37.069 Caio Velasco: If it’s not canceled, then you have this or something
604 01:12:43.160 ⇒ 01:12:46.390 Caio Velasco: which is not approved, it does involve cancel.
605 01:12:46.650 ⇒ 01:12:51.689 Caio Velasco: Yeah, it could be the case. Right? Yeah. So order was canceled because the seller canceled
606 01:12:52.110 ⇒ 01:13:01.180 Luke Daque: Hmm, yeah, I don’t think this is order status. No, it’s easy. Ship shipment status.
607 01:13:07.420 ⇒ 01:13:14.519 Luke Daque: This one is the order. Statuses canceled orders. Status doesn’t say if it’s
608 01:13:15.250 ⇒ 01:13:17.420 Luke Daque: if the payment happened or not.
609 01:13:19.630 ⇒ 01:13:22.479 Luke Daque: can we? Is there any refunds table
610 01:13:23.170 ⇒ 01:13:24.130 Caio Velasco: Refund.
611 01:13:24.830 ⇒ 01:13:28.500 Luke Daque: Yeah, in the in Snowflake, can we try? Yeah, like, maybe there.
612 01:13:42.110 ⇒ 01:13:44.710 Luke Daque: cause what what I was thinking is like, if
613 01:13:44.920 ⇒ 01:13:49.960 Luke Daque: if the cancelled order Ids is in any of the refund table. It means that
614 01:13:50.820 ⇒ 01:13:55.689 Luke Daque: the payment happened, and then Amazon is just refunding the payment right
615 01:13:56.540 ⇒ 01:14:02.869 Caio Velasco: Girls. Yes, then it could be. There’s 1 financial service
616 01:14:03.400 ⇒ 01:14:09.230 Luke Daque: But but that doesn’t have any order, Id, though, so we won’t be able to query the order.
617 01:14:09.540 ⇒ 01:14:10.130 Luke Daque: There
618 01:14:10.130 ⇒ 01:14:10.520 Caio Velasco: Yeah.
619 01:14:10.520 ⇒ 01:14:11.360 Luke Daque: If that
620 01:14:12.940 ⇒ 01:14:13.740 Caio Velasco: Harder, number
621 01:14:17.640 ⇒ 01:14:19.380 Luke Daque: Sales traffic reports.
622 01:14:20.620 ⇒ 01:14:21.950 Luke Daque: Yeah, I don’t.
623 01:14:23.720 ⇒ 01:14:26.360 Luke Daque: I don’t think that has order Id either.
624 01:14:27.910 ⇒ 01:14:35.430 Caio Velasco: There’s only 3 3 refund strings here. It’s like, basically good.
625 01:14:39.050 ⇒ 01:14:40.810 Caio Velasco: Yes, there’s nothing here
626 01:14:40.810 ⇒ 01:14:45.500 Luke Daque: This morning it sucks well.
627 01:14:45.500 ⇒ 01:14:48.469 Caio Velasco: Oh, interesting! But the refund is a big thing.
628 01:14:48.550 ⇒ 01:14:49.990 Luke Daque: Exactly. Yeah.
629 01:14:55.410 ⇒ 01:14:59.999 Caio Velasco: They’re under sun inventory plus not really right.
630 01:15:01.100 ⇒ 01:15:07.680 Luke Daque: Unless it’s and unless it’s in the transaction type, right transaction type equals refund
631 01:15:08.970 ⇒ 01:15:10.779 Caio Velasco: Oh, then we should look here.
632 01:15:14.150 ⇒ 01:15:15.283 Caio Velasco: I’m sure.
633 01:15:17.340 ⇒ 01:15:20.500 Caio Velasco: 7
634 01:15:31.470 ⇒ 01:15:32.220 Luke Daque: Yeah, that’s
635 01:15:37.690 ⇒ 01:15:39.130 Luke Daque: but yeah, I don’t know if, like.
636 01:15:46.410 ⇒ 01:15:51.410 Luke Daque: Important. This question is at the moment, because, like, if we, we are spending like a
637 01:15:52.290 ⇒ 01:15:59.200 Luke Daque: a couple of hours just to answer this question. And then it’s not really that important like today.
638 01:15:59.200 ⇒ 01:16:05.309 Caio Velasco: So that’s the thing like I don’t know the level of the importance. I just know that is urgent. Everything is urgent
639 01:16:05.720 ⇒ 01:16:07.030 Luke Daque: Yeah, that’s
640 01:16:07.030 ⇒ 01:16:09.989 Caio Velasco: The level of importance. I have no idea
641 01:16:11.040 ⇒ 01:16:11.870 Luke Daque: Yeah.
642 01:16:14.920 ⇒ 01:16:20.497 Caio Velasco: I can update at least like the What Akash asked.
643 01:16:21.856 ⇒ 01:16:25.900 Caio Velasco: Which is basically updating the tickets with everything that we just stopped
644 01:16:26.190 ⇒ 01:16:27.130 Luke Daque: Yeah.
645 01:16:31.460 ⇒ 01:16:33.620 Caio Velasco: And where did you get this from
646 01:16:35.390 ⇒ 01:16:36.100 Luke Daque: Which one?
647 01:16:36.600 ⇒ 01:16:40.010 Luke Daque: Oh, that was Chat Gpt, that I tried to ask. Yeah.
648 01:16:40.300 ⇒ 01:16:41.360 Caio Velasco: It’s second.
649 01:16:41.360 ⇒ 01:16:46.920 Luke Daque: And its answer makes sense. But we don’t really have data to back it up.
650 01:16:50.710 ⇒ 01:16:52.630 Luke Daque: But maybe you can
651 01:16:52.630 ⇒ 01:16:53.490 Caio Velasco: Basically
652 01:16:56.690 ⇒ 01:16:57.480 Caio Velasco: right
653 01:16:58.330 ⇒ 01:17:05.830 Luke Daque: Yeah, I was like saying, like, we can, you can say that like, based on what we saw here from this query that you did
654 01:17:06.446 ⇒ 01:17:13.060 Luke Daque: there were no orders that were fulfilled with the status canceled.
655 01:17:13.280 ⇒ 01:17:17.370 Luke Daque: But yeah, something like that. I don’t know
656 01:17:19.690 ⇒ 01:17:28.719 Caio Velasco: Yeah, I think we’ve already said below, we’re also we also or refund.
657 01:17:39.170 ⇒ 01:17:40.260 Caio Velasco: Confirm.
658 01:17:42.056 ⇒ 01:17:48.789 Caio Velasco: Think something in the password.
659 01:17:58.780 ⇒ 01:17:59.880 Caio Velasco: Alright.
660 01:18:09.980 ⇒ 01:18:14.690 Caio Velasco: Okay. I think I understand what I, what I what at least what we did now like.
661 01:18:14.970 ⇒ 01:18:22.989 Caio Velasco: If if we were to divide this very broadly, 3 things, it’s like goal cancellation, free cancellation element.
662 01:18:23.440 ⇒ 01:18:26.630 Caio Velasco: I can be even more human than refund.
663 01:18:28.210 ⇒ 01:18:41.230 Caio Velasco: Then I could. I can try to explain all the potential websites and then look for data in all the positions, cancellation and refund cancellation and
664 01:18:41.700 ⇒ 01:18:45.640 Caio Velasco: payment, and whatever. And then for all kinds of
665 01:18:46.581 ⇒ 01:18:55.000 Caio Velasco: possibilities, we start to like, go into the database, and see there is anything either in our no faith or things that we’re not even in justice.
666 01:18:55.100 ⇒ 01:18:58.080 Caio Velasco: and maybe do the fine book cool.
667 01:18:58.770 ⇒ 01:19:01.399 Caio Velasco: There’s not something that you can do right
668 01:19:03.300 ⇒ 01:19:05.680 Luke Daque: Yeah, I think, so, yeah.
669 01:19:09.140 ⇒ 01:19:13.739 Caio Velasco: Okay, I think that’s a great step right to start. I will post over there on slack
670 01:19:14.290 ⇒ 01:19:15.749 Caio Velasco: see what they think.
671 01:19:16.410 ⇒ 01:19:25.293 Caio Velasco: Yeah, let’s see, I mean, I don’t even know. What kind of feedback would they get? Would they give us? Because they also don’t have the knowledge of this right
672 01:19:26.230 ⇒ 01:19:26.990 Luke Daque: Yeah.
673 01:19:30.730 ⇒ 01:19:33.849 Luke Daque: If do you do, you have one password right?
674 01:19:34.620 ⇒ 01:19:35.380 Luke Daque: Installed
675 01:19:35.380 ⇒ 01:19:36.030 Caio Velasco: I do?
676 01:19:38.268 ⇒ 01:19:42.149 Luke Daque: I yeah. I think the 5 grand access end up
677 01:19:42.630 ⇒ 01:19:51.489 Luke Daque: should be in in one password. So I think you can also see there like if you want to see how 5 trend looks like for jabby coffee
678 01:19:53.840 ⇒ 01:20:01.269 Luke Daque: and like, just so you get to know, like like, what tables we are ingesting. And what tables we are.
679 01:20:02.110 ⇒ 01:20:04.630 Luke Daque: Not ingesting, for example.
680 01:20:05.700 ⇒ 01:20:09.769 Luke Daque: Yeah, it’s also it’s also like good to be at least
681 01:20:10.070 ⇒ 01:20:12.559 Luke Daque: see what it looks like in 5 chat
682 01:20:16.210 ⇒ 01:20:16.820 Luke Daque: and
683 01:20:17.470 ⇒ 01:20:24.960 Caio Velasco: I never even logged into 5 sense to be honest, but never even purchase anything ingestion related
684 01:20:30.300 ⇒ 01:20:34.830 Luke Daque: Yeah, it’s it’s good to see that as well. So so at least you have an idea.
685 01:20:35.370 ⇒ 01:20:39.560 Luke Daque: since you already are looking at the Erd and the Api stuff
686 01:20:39.560 ⇒ 01:20:39.880 Caio Velasco: That’s right.
687 01:20:39.880 ⇒ 01:20:42.070 Luke Daque: Maybe it’s also good to see the Ui
688 01:20:44.470 ⇒ 01:20:46.840 Caio Velasco: This is the year with Javi. Right, I guess.
689 01:21:00.970 ⇒ 01:21:03.319 Caio Velasco: would be this one, I assume right
690 01:21:05.500 ⇒ 01:21:06.370 Luke Daque: Yeah.
691 01:21:12.710 ⇒ 01:21:16.539 Caio Velasco: Okay, okay, I’ll try to check in as well.
692 01:21:17.580 ⇒ 01:21:19.080 Luke Daque: Yeah. Can you try logging in
693 01:21:21.210 ⇒ 01:21:22.800 Caio Velasco: Either one right, maybe
694 01:21:23.163 ⇒ 01:21:29.709 Luke Daque: Maybe maybe that one the the Javi coffee one. Because if you use it, might send an Otp
695 01:21:30.570 ⇒ 01:21:31.490 Luke Daque: to his.
696 01:21:32.545 ⇒ 01:21:33.260 Luke Daque: Yeah.
697 01:21:37.780 ⇒ 01:21:43.470 Luke Daque: near that one to what happened
698 01:21:44.170 ⇒ 01:21:44.809 Caio Velasco: You got it
699 01:21:46.110 ⇒ 01:21:48.449 Luke Daque: I don’t know what. Let’s try again.
700 01:21:51.650 ⇒ 01:21:52.530 Caio Velasco: Oh, weird!
701 01:21:54.630 ⇒ 01:21:59.640 Luke Daque: It’s not even saying password, wreck, or something. It just
702 01:22:00.490 ⇒ 01:22:03.410 Caio Velasco: Can I copy from
703 01:22:04.380 ⇒ 01:22:05.869 Luke Daque: Yeah, let’s try that
704 01:22:10.900 ⇒ 01:22:12.369 Caio Velasco: Oh, that’s weird!
705 01:22:12.860 ⇒ 01:22:13.940 Luke Daque: Yeah. That was weird.
706 01:22:22.350 ⇒ 01:22:23.500 Caio Velasco: Connections.
707 01:22:23.500 ⇒ 01:22:25.609 Luke Daque: There you go. Yep. Connections.
708 01:22:25.760 ⇒ 01:22:36.740 Luke Daque: you can see. Yeah. Amazon is the only thing active now now, and the rest, I believe, have been like moved to portable. So you can see recharge. You can do gorgeous. They are all paused
709 01:22:36.880 ⇒ 01:22:40.450 Luke Daque: because we’re using portable now.
710 01:22:40.770 ⇒ 01:22:44.120 Luke Daque: But yeah, Amazon is still active, and if you click on
711 01:22:44.660 ⇒ 01:22:46.449 Luke Daque: the drop down at the left.
712 01:22:48.640 ⇒ 01:22:52.580 Luke Daque: or maybe just click on Amazon connection
713 01:22:53.140 ⇒ 01:22:56.019 Luke Daque: and then schema at the top.
714 01:22:57.630 ⇒ 01:23:00.520 Luke Daque: But yeah, here is where you can see, like
715 01:23:01.850 ⇒ 01:23:06.488 Luke Daque: in the status, what the status is like. Like, even the
716 01:23:07.370 ⇒ 01:23:10.649 Luke Daque: yeah, in the schema. That’s the tables that we are
717 01:23:11.240 ⇒ 01:23:20.729 Luke Daque: ingesting. You can see those that don’t have check marks in them are the tables that we are not ingesting like inbound shipment. We’re not just
718 01:23:20.730 ⇒ 01:23:29.310 Caio Velasco: So 5 different can see all paper from the I don’t know the endpoint at Amazon. And then here we select what we want
719 01:23:29.310 ⇒ 01:23:30.540 Luke Daque: Yes, that’s correct.
720 01:23:31.800 ⇒ 01:23:36.490 Luke Daque: And all the tables there should be based on the Erd.
721 01:23:38.470 ⇒ 01:23:42.300 Luke Daque: the Google that we were looking at right? So like.
722 01:23:42.610 ⇒ 01:23:44.680 Luke Daque: you can also see from there
723 01:23:45.950 ⇒ 01:23:51.420 Luke Daque: what the field should be, and like, what are the primary keys and stuff like that
724 01:23:53.960 ⇒ 01:23:54.470 Caio Velasco: Yeah.
725 01:23:55.010 ⇒ 01:24:00.270 Luke Daque: And if you really like, yeah, cool.
726 01:24:02.840 ⇒ 01:24:14.750 Caio Velasco: So I’ll I’ll leave you now, then, so that take more of your time. But, thank you, man, I really appreciate. It was quite helpful. There’s a lot of things here that I didn’t know, and even the work of the investigating this without any
727 01:24:15.010 ⇒ 01:24:22.830 Caio Velasco: connection to the client. I I have never done this. That’s why I didn’t know that. That’s what’s what I was supposed to do.
728 01:24:23.180 ⇒ 01:24:26.216 Caio Velasco: because at the end of day, you see, we don’t have any any
729 01:24:27.330 ⇒ 01:24:28.129 Luke Daque: Yeah, cool.
730 01:24:28.670 ⇒ 01:24:29.280 Caio Velasco: It’s nice
731 01:24:29.280 ⇒ 01:24:29.860 Luke Daque: Sounds good
732 01:24:29.860 ⇒ 01:24:31.259 Caio Velasco: Thank you. Ever appreciate it.
733 01:24:31.260 ⇒ 01:24:36.080 Luke Daque: No problem. Just message. If you, if you still need anything or you have any questions
734 01:24:36.820 ⇒ 01:24:39.230 Caio Velasco: Okay, would do sounds good, perfect.
735 01:24:39.820 ⇒ 01:24:40.799 Caio Velasco: Thank you.
736 01:24:41.010 ⇒ 01:24:41.650 Luke Daque: Bye, bye.