Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am trying to solve the following logical problem:
- I have a lot of storage_areas with names like "KT1", "KT2" ... up to "KT75" and "KT101" up to "KT175".
- In addition to those, there are areas with names like "KT1OUT", "KT2OUT" etc. up to "KT75OUT" and "KT101OUT" up to
"KT175OUT".
- The areas "KT1" and "KT101", however, are actually just one, the names are just used for different purposes.
- Likewise, "KT1OUT" and "KT101OUT" are one unit.
- Bookings (of goods into the database) can occur on both "KT1" and "KT101" and so on.
- I already have a table (a "database" I'm just building up in Excel) with a number of shelves we have here.
=> I would like to concatenate the list of these to it, but I cannot think of the right way to do this:
- If I concatenate the entire list, I would end up with double the storage_space as KT1 and KT101, which are actually just one area
with 5 places, would end up with twice that.
- If I do a mapping (in Excel) that would assign the name "KT1" to both KT1 and KT101 and I load that with a DISTINCT, the amount
of storage_space would be correct, but I would potentially lose any items booked on KT101.
I hope you can follow me so far. It is complicated enough. I needed a while to understand it, and even now I'm not so sure ...
One possible solution I could come up with is, I have to assign the storage_areas I have in the "real" database a new name, which would make all items which were booked on KT101 appear as booked on KT1 and so on. Then I could do that with the LOAD DISTINCT and I would not lose out on any items.
Maybe, however, someone has a better idea? Any suggestions are welcome.
Hi Marcus,
this is solved for now.
The reason is indeed that there are other formulas to show even if a link isn't possible - I have deactivated all other formulas, and then those areas where there is no linked data were gone.
It's not a problem, however. Indeed, these are wanted in the chart. The information of how many potential storage_areas we are not using at any given time is also important.
So this is also solved 😉
I guess the next problem is just around the corner, so let's have a look ...
Best regards,
DataNibbler