As the packages don't carry a created date, and it is very difficult to identify which payware comes in which package, any list is going to be something of a guess. But start with this:I agree, items that are on the DLS at the time the package is built should never be marked payware. That suggests that the item was not on the DLS at the time the package was built.
3DZ Coil 2200mm Large (PR),<kuid2:212731:500122:2>
3DZ Coil 2200mm Small (PR),<kuid2:212731:500123:2>
3DZ Coil 1800mm Large (PR),<kuid2:212731:500124:2>
3DZ Coil 1800mm Small (PR),<kuid2:212731:500125:2>
3DZ Coil 1400mm Large (PR),<kuid2:212731:500126:2>
3DZ Coil 1400mm Small (PR),<kuid2:212731:500127:2>
3DZ Coil 800mm Large (PR),<kuid2:212731:500128:2>
3DZ Coil 800mm Small (PR),<kuid2:212731:500129:2>
Why does that matter? The effect on the user is the same. If a subscription is suspended for a period, or the user chooses to go off line for a period, they should have access to everything on the DLS, regardless of whether it was placed there before or after their payware package was created.It may have been uploaded since
Uh? The issue is about items that are on the DLS and are also payware. Payware that isn't also a DLS item does not create a problem.... or it may in fact not be available on the DLS at all.
That is indeed a different problem, specific to route builders who try to ensure that no payware in included in their route, and find that the asset kuid gets upversioned to the payware version by default.(Please don't confuse this with the case where an older version is on the DLS, but the payware includes a newer version which has not yet been released as a free download.)