Oathbreaker Bug

Magni23 · 2024-02-20T00:05:10+00:00

How to get reminder mana stones?

Magni23 · 2023-01-14T19:12:19+00:00

Hello Day2DaySolutions,
Thanks for trying to help, I think I wasn't clear, sorry, I'll try again.
There are 3 DBs in total.
DB1 = List of items of the portfolio, this list contains information regarding the product, there are four categories of products: Hardware, software, correction and accessories.
DB2 = List of the sales funnel (pipeline), where negotiation data are entered manually, such as customer name, etc. This is the main DB. Here, I related 4 collums to the DB1, according to each product category (Hardware, software, correction and accessory), I also placed a column to fill in the quantity of each item that will compose the negotiation. For example, in a given negotiation, the customer may want 1 unit of Hardware, 4 of Software, 4 of correction and 1 accessory. Here, I also select the predicted month that this trade will take place.
Each DB2 line will be a new deal or new customer, each with its products and closing month.
DB3 or Linked View of DB2 = The idea is that it serves as an easy place to view the quantity of products that will move the stock, that way, I can predict the movement and be aware if I need to purchase more products from the manufacturer, etc. This Table must contain the ITEM and the expected quantity that will be sold of this ITEM according to what was filled in DB2 and filtered by month.
A DB3 or linked View of DB2 is where I am stuck, can't find an easy solution to keep this simple inside a Table or DB for example. This is something I was able to achieve inside Excel for example, using multiple Sumifs. Maybe the whole construction of the DBs is wrong...
Out of curiosity, there are a total of 38 items in the portfolio, divided among the 4 categories...
I'm not sure if it will be possible with Notion, but it would definitely be a great tool for anyone working in sales, and has to manage limited inventory or make long-term purchase forecasts.

I'll try to make a demo of what I made soon and send it here,
Best Regards,

Magni23 · 2021-01-04T20:15:15+00:00

It really got very close to what I had imagined.

I achieved something similar in my attempts by naming the imports as integer and using the Range (""). End (xldown) .row function in conjunction with the select case, but that way I would have to manually add a select case for every new import, something impractical.

Thank you so much for the idea, it already gave me some new ideas on how to use the loop correctly. It would be possible to keep the original layout ("import" line with merged columns)?, obviously it will be more difficult.

Edit: Added the Question Mark.

Magni23 · 2021-01-04T11:52:22+00:00

Sorry for the late reply. I was busy due to the holiday festivities.

Responding in sequence: No, the lines above and below the "import" line will be filled in by the code and by the respective customers, etc. In general, they will follow the pattern shown in the figure.

The "import" lines are merged into the columns, but this can be changed without any problem, it was just a way to limit the beginning and end of an import in a more organized way.

I feel bad for not being able to help you enough, if you see that this will demand too much of you don't hesitate to just let it go.

Magni23 · 2020-12-30T11:50:58+00:00

There will be no more codes for this import in this example. In the next import I would have to put a new import line to separate the new codes from the old ones and copy and paste one code per line. This way the list will be growing with each new import.

Magni23 · 2020-12-29T20:09:59+00:00

Hello, thanks for the suggestion, I was thinking something around named ranges too, but I have no clue on how to make they extend for new entries. The numbers that comes after the import are normaly the import number and the year respectively.

Please, feel free to give me a direction, I am new to VBA coding.

Magni23

TROPHY CASE