Precisely Enterworks

Hi Ryan,

Try using the Custom Dropdown List Dynamic option,  but use the following SQL instead:

SELECT Vendor_Name as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

For the 'Description' and 'Code' fields, feel free to use whatever attributes you would like form the Vendor repository (as long as they are relational in the model).  I usually add a WHERE clause as well to include only "active" values and an ORDER BY to make the list alphabetical, etc..  This will add allow the dropdown list to appear quickly and be 

Ex:

SELECT Vendor_ID as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

WHERE Vendor_Status = 'Active'

ORDER BY VENDOR_NAME ASC

I hope this helps.  Let me know if you have any other questions.

Thanks,

Eric Gilboe

Amplifi

Practice Director - Precisely

Cell: 480-284-3296

www.goamplifi.com

Hey Eric,

Thanks for the reply!  Unfortunately, that didn't work for me either.  It's still very slow to load and unusable.  I even get the nice pop-up prompt from my browser saying that the page isn't responding and asks if I want to wait or exit. Sometimes that pop-up comes up a few times, but if I click wait it does finally load.  But it's impossible to scroll through the list once it does because it's so slow and the browser seems to freeze up again.  Am I still doing something wrong? 
The really old system we are trying to replace currently does this, so I'm hoping it can be done here with Enterworks as well.

I can set it up with a loaded codeset of the Vendors and that seems to work just fine.  But that is a static list.  I know we could probably do it a roundabout way of exporting and importing into a codeset and use that instead.  But then the users still wouldn't be able to add a new vendor and immediately associate the items with them without having to first wait for an export/import job to run at some interval to load the codeset with that new vendor.  Which is not ideal and really slows productivity.

Thanks for the help!

Hi Ryan,

Try using the Custom Dropdown List Dynamic option,  but use the following SQL instead:

SELECT Vendor_Name as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

For the 'Description' and 'Code' fields, feel free to use whatever attributes you would like form the Vendor repository (as long as they are relational in the model).  I usually add a WHERE clause as well to include only "active" values and an ORDER BY to make the list alphabetical, etc..  This will add allow the dropdown list to appear quickly and be 

Ex:

SELECT Vendor_ID as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

WHERE Vendor_Status = 'Active'

ORDER BY VENDOR_NAME ASC

I hope this helps.  Let me know if you have any other questions.

Thanks,

Eric Gilboe

Amplifi

Practice Director - Precisely

Cell: 480-284-3296

www.goamplifi.com

Hey Eric,

Thanks for the reply!  Unfortunately, that didn't work for me either.  It's still very slow to load and unusable.  I even get the nice pop-up prompt from my browser saying that the page isn't responding and asks if I want to wait or exit. Sometimes that pop-up comes up a few times, but if I click wait it does finally load.  But it's impossible to scroll through the list once it does because it's so slow and the browser seems to freeze up again.  Am I still doing something wrong? 
The really old system we are trying to replace currently does this, so I'm hoping it can be done here with Enterworks as well.

I can set it up with a loaded codeset of the Vendors and that seems to work just fine.  But that is a static list.  I know we could probably do it a roundabout way of exporting and importing into a codeset and use that instead.  But then the users still wouldn't be able to add a new vendor and immediately associate the items with them without having to first wait for an export/import job to run at some interval to load the codeset with that new vendor.  Which is not ideal and really slows productivity.

Thanks for the help!

Hi Ryan,

Try using the Custom Dropdown List Dynamic option,  but use the following SQL instead:

SELECT Vendor_Name as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

For the 'Description' and 'Code' fields, feel free to use whatever attributes you would like form the Vendor repository (as long as they are relational in the model).  I usually add a WHERE clause as well to include only "active" values and an ORDER BY to make the list alphabetical, etc..  This will add allow the dropdown list to appear quickly and be 

Ex:

SELECT Vendor_ID as 'Code', Vendor_Name as 'Description'

FROM VENDOR_STAGING

WHERE Vendor_Status = 'Active'

ORDER BY VENDOR_NAME ASC

I hope this helps.  Let me know if you have any other questions.

Thanks,

Eric Gilboe

Amplifi

Practice Director - Precisely

Cell: 480-284-3296

www.goamplifi.com