AWS-ZachErdman
AWS-ZachErdman
> Definitely a very important need. This has been discussed as a part of the SKU. @AWS-ZachErdman thoughts on if this can be a fast follow or if you consider...
> Absolutely! This is what #315 is all about 🙂 We discussed this leading up to the preview and just weren't able to lock it down. We were in agreement...
I'd be interested in starting a task force on this if we haven't yet, or joining the existing one!
Agree with Irena - maybe we can close and link to 495 for history
I felt the third explained a lot of what the benefits of amortization are, but without explaining how a provider should do it. I like the idea of creating a...
I read the column descriptions and started going through the sample data which is very detailed, but I'm wondering if there is any documentation anywhere that clearly explains the use...
I'm interested in this one for v1.1
> @AWS-ZachErdman Seems like we'll need a good amount of supporting content to be added here to capture all the discussions and how we ended up getting around to this....
this makes sense as an alternative for adding an ID column, but this PR is missing the use cases of: 1/ used vs unused status 2/ capacity total
https://docs.google.com/document/d/1zPEUZ5L5wf9YAJ63ymW3tyrOFx-krJBB6sf1bHU_oOs/edit Need input from other providers to get their first class columns that differentiate between different SKUs and different SKU Price IDs