Developer forum

+1

Hi Guys,

We have a planned feature for refactoring HOW assortments work, so I will add a link to this thread.

I cannot promise things will be changed as part of this refactoring, but we will consider what we can do as part of the rewrite.

TFS #48217

BR

Martin

Thank you very much Martin.

Is this planned for 9.5?

Thanks,

Adrian

It is planned for 9.5, but it does not have the highest priority, so if things are cut, this might be one of them.

Hi Martin,

What are the estimates in this case?

Best case scenario, it makes it to 9.5 (august) and we have a chance to have a stable version of it by January 2019.

Worse case, it does not make it to 9.5 which means next option is 9.6, meaning a stable version by January 2020.

It looks like, if it does not make it to 9.5, we are on our own. Not a pretty perspective since a lot of the recent projects are using assortments.

Thank you,
Adrian

Hi Adrian

It depends on how many questions you ask...! If we spend all summer answering questions like this, you get no code :-).

We try our hardest to prioritize all the requests and get as much of them done as possible - that is in our interest!

Thanks, Nicolai

Hi Nicolai,

If my posts are keeping you from developing it, I would gladly stop :)

The fact is that my first post on this issue was on december 2016 (http://doc.dynamicweb.com/forum/feature-requests/feature-requests/sort-assortments-lists) and the next ones are in January 2017. I stopped posting anything on the subject hoping for a change. 9.4 is out and there is still no sign on improvements.

That's why I see my last comment above merely a state of the obvious than a question.

The problem with all these nice functionalities (or at least some of them) is that they are incomplete. And becuase we have to custom develop something to solve it,  it's like selling the website for 100 and asking 5000 for the back-end of it.

If the assortment functionalities cannot be managed easily, it's like not having an admin at all. I agree, I may exaggerate a bit.

You have mentioned in a different post to check the list of functionalities and avoid asuming something will work in a specific way. Sales people are actually selling those functionalities. They don't care about how they really work or how they are implemented. They call it "standard". Then, in the implementation or afterwards, you have to explain to the customer that standard means something else.

I am probably one of the few species of a combined Sales and Developer. And because of that I have to face both sides of the problem. Selling it and Implementing it. And I am concerned about what I promise because I want to actually deliver the promise.

And these 2 customers that I already have, they have received my promise more than a year ago. And nothing happened. And if you can't help me deliver, I need to do it on my own. Which means that instead of using something standard, I have to build something custom on my own time and money just to augment a standard functionality. Not cool.

That's my 5 cents on this issue and I will stop asking you about it. If it will be in 9.5, fine. If not, it's fine as well. I will figure out a solution on my own.

Thank you,

Adrian