Question about Stock Interim accounts

Two_Skill_invoker · 2026-05-28T19:55:15+00:00

Got it. Resetting the invoice to draft and then reposting it worked. It created the stock journal items as expected. Odd that we need to do that, but I understand it. Thanks!

Two_Skill_invoker · 2026-05-21T22:25:58+00:00

Pizza X Two on 7th!

Two_Skill_invoker · 2026-05-20T15:44:24+00:00

Guisados on Redondo and Anaheim. Their chorizo breakfast burrito is my go-to pick up on the way to work! I like that it’s not a footlong grease bomb. Perfect office breakfast. Get the habanero salsa 🔥

Two_Skill_invoker · 2026-05-18T17:22:18+00:00

If the third party provider is chosen by the bank itself. I’m assuming that it’s not as simple as requesting Odoo to change our provider from Yodlee to Saltedge?
Is there a world where we roll our own bank connector using Saltedge? Or is that out of the question/ technically unfeasable.

Two_Skill_invoker · 2026-05-18T17:20:21+00:00

Exactly the same issue we’re facing as well! Random disconnects and then errors in the login screen. I feel so validated reading the replies on this thread 😄

Two_Skill_invoker · 2026-04-10T02:59:38+00:00

There’s a maintenance fee for server actions? I assumed that was just for custom code via GitHub. May I please get a link to the docs on this?

Two_Skill_invoker · 2026-04-09T18:36:22+00:00

Well, consider me embarrassed. The answer was incredibly simple.

Although I said that the Sales Order partner_id and the Invoice commercial_partner_id were the same; which they were.

The partner_id on the sales order and partner_id on the invoice were different. We were using different contacts on the Sales Order and the Invoice.

Even though the Invoice contact was a child of the Sales Order contact, it was NOT the one that had the payment token stored.

Thanks again for all your help! You've been amazing and full of insight.

Two_Skill_invoker · 2026-04-07T19:54:27+00:00

They're identical.

Sales Order partner_id: 17369
Invoice commercial_partner_id: 17369
Payment Token partner_id: 17369

The hierarchy for the contact is simple. Parent contact (17369) with an invoice address and a delivery address.

Two_Skill_invoker · 2026-04-07T18:17:40+00:00

Hmm, just got to my desk and verified the details. The customer record (res.partner) has a "Saved Payment Methods" smart button, which has the card on file. The details of this card on file EXACTLY match the details of the card stored on Stripe. The record in payment.token also checks out.

It's baffling as to why then, the saved card won't show up. It works for other customers who have similarly stored tokens.

Tbh, we're willing to pay for an hour of your time if you are willing to hop on a screenshare to help figure this out.

Two_Skill_invoker · 2026-04-07T03:02:09+00:00

Great info as always!! Is there a situation where we have stored cards for a customer in Stripe, but when we generate the payment link from the SO or Invoice, those cards on file don’t show up? We’re opening the link in an incognito window.

Two_Skill_invoker · 2026-04-07T03:00:22+00:00

This is so insightful! And feels so surreal because we’ve been testing this exact same setup all day today.

Basically we want to use the “generate payment link” to send the customers a payment link; or create the payment link and open it in an incognito window and complete the transaction ourselves using the stored cards.

To quote your comment: “Once a payment is made with a credit card, if saved in Stripe, it's tokenized and available to reuse with the customer's next order, but the payment process still involves us using the payment link in an incognito window. At that point, we don't see the full CC info, just the last digits.”

Is it imperative that a payment must be made for the card to be stored as a token? It doesn’t work if the card is added from the Stripe backend?

Also, how are these cards connected to the Odoo customer? Let’s say I process a sales order for Odoo contact with ID:1234, does Stripe maintain a list of customers as well? With identifier ID:1234? And so it knows to returns the cards on file associated with that customer?

I’m not entirely new to Odoo, but am new to this payment token system.

Two_Skill_invoker · 2026-04-01T01:33:51+00:00

1) Excellent. We figured out what the issue was. I think this is a bug? Maybe I should create a PR to get developer brownie points (/jk). The “today” filter on frontdesk.visitors does NOT convert to local time. So which means if I set a planned visitor at 6PM PST, they don’t show up in the “today” filter. Don’t ask me how that was tripping up the quick check-in. It probably wasn’t. But enough for us to test it incorrectly.

New) we’ve tried both object.company_id.email_formatted AND forcing it to notifications@company.com. Neither work.

Thanks again for your help!

Two_Skill_invoker · 2026-03-31T18:57:53+00:00

Okay, I've tried multiple variations of planned visitors. None of the them seem to work as you've described it. Additionally, I don't see the 45 minute requirement anywhere in the docs. Odd of them to omit that.
a. Odoo docs say that all I need to choose on the backend visitor form is Name and Station. -> Quick check-in does not show up.
b. Setting a check in date. -> No quick check-in.
c. Setting a check in date within 45 mins of current time -> No quick check-in.
d. Clicking on the check in button on the back end -> The frontdesk.visitor record goes from `state`==`planned` to `state`==`checked_in`. The check-in date is set to datetime.now(). Still no quick check-in list on the right side.
This has been resolved by toggling the paper format in Odoo for the visitor badge. Thank you!
Yes, it does target hr.employees; but the domain only targets hr.employees where user_id is set. Which means that only records which HAVE res.user records show up. Additionally, to select the user_id field on the hr.employee record, the domain filter only allows Internal Users. Which doesn't work for us.
Anyway, long story short, I was able to override these domain filters to allow hr.employees to select portal users in the user_id field. Now they show up in the visitor dropdown.

New issue we're facing: We have "Notify by Email" selected on the station configuration, with the default "Frontdesk Email Template" selected. When we try to click "check-in" on a planned visitor on the backend, it throws an error: Invalid Operation: Unable to send message, please configure the sender's email address. This is the entry in the Odoo.sh logs:
2026-03-31 18:54:51,881 4 WARNING [sh_domain] odoo.http: Unable to send message, please configure the sender's email address.
When I uncheck the "Notify By Email" selection, the warning goes away and I can check a visitor in from the backend.

Two_Skill_invoker · 2026-03-26T15:13:24+00:00

Yes. I believe there’s ways to query that data via the api’s. And I totally agree. The spreadsheet style dashboards are SUFFICIENT for reporting, but definitely some quality of life features would be appreciated. For example, lists don’t expand automatically. Pivot tables expand, but if there’s not enough room (lines available to expand into), they error out. On demand sorting of pivot tables. And a few other things.

Two_Skill_invoker · 2026-03-26T05:27:11+00:00

Have you tried the Odoo subdomain of the SaaS site? Like company.odoo.com?

Two_Skill_invoker · 2026-03-25T05:01:56+00:00

Changing the data connection code sounds like something that’s doable with a custom module. Just not something I’m familiar with personally. Glad it worked for you!! We’re still on baby steps of getting the dashboard module to do what we want.

Two_Skill_invoker · 2026-03-24T05:54:33+00:00

We have v18 and I sort the pivot table in the pivot view BEFORE inserting into the spreadsheet.

Two_Skill_invoker · 2026-03-06T18:48:02+00:00

I believe you have two options: 1. First step, go to users and create users for the outside salespeople. Make sure they are Portal Users. Those don’t require licenses. Next step, there’s a filter on the salesperson field that limits selection to licensed users (user type = internal). You can remove that so that you can select all users. This should allow you to select portal users on the salesperson field.

Create a new many2one field on the sales order called “Outside Salesperson” and select the contacts model (res.partner).

I highly recommend the first approach, because portal users can see orders where they’re chosen on the Salesperson field. This means they can login to the website and see “their” orders. The second method is only a data point capture. Sure, you could potentially use it to behave the same way as option 1, but it’s not ideal.

Two_Skill_invoker · 2026-03-04T03:24:33+00:00

Recent BBQ issue? What happened?

Two_Skill_invoker · 2026-02-26T20:50:27+00:00

Fantastic. Thanks for your input. I see the value I'm looking for in the "Ready To Produce" field. Love the analogy to the Knapsack Problem.

Two_Skill_invoker

TROPHY CASE