This output cookbook is amazing and super helpful, thank you!
But hoping someone can help me with an error I am getting (below) when trying to add multiple phones. I tried it with 'VS_ELEMENTS_PHONE' and it worked, but then I got an error when trying to add parameters.
Thanks in advance!!
Updates of TR_QUERY_ELEMENT_GROUP FAILED.50000 : SQLSTATE = 42000Microsoft OLE DB Provider for SQL ServerInvalid object name 'LVS_ELEMENTS_PHONE'.
No changes made to database.
INS ERT INTO TR_QUERY_ELEMENT_GROUP ( description, data_from, virtual_ind, category ) VALUES ( 'Phones ALL', 'LVS_ELEMENTS_PHONE', 'N', 124 )
Came back to add that I've tried a couple of others (Expired constituencies) and they aren't working either. Anyone know what might be happening?
If you copied this output from the cookbook then the name of the view is LVS_ELEMENTS_OTHER_PHONE.
oh. I have this...?
Column Name
Example Value
Description
Phones ALL
Data_From
LVS_ELEMENTS_PHONE
Data_Where
[Blank]
Virtual Ind
[Unchecked]
Category
Phone Information
Ah, you're using the Output All Phones. I was looking at the Other Phone output, which is the one we use. Did you created the view LVS_ELEMENTS_PHONE? If so, try refreshing your views and trying again
I'm not sure about creating the view, I followed the above and it wouldn't save? Tried a few times. What is the other one you use and what is the difference? I just want to be able to choose the phone types to output...
We use the one called Other Phone, it allows us to select multiple phone types. So we can output cell, business, etc. in it's own column. It's the one right below Output All Phones in the cookbook.
I think I tried that one also! Will revisit and make sure. Thank you!
Anyone know why the LVS_ELEMENTS_PHONE may not be working? I've actually tried a few and none are working for some reason? Help?
A lot of the cookbook recipes require a new custom view to be created in SQL Server Management Studio (SSMS) rather than relying on tables or views that already exist. The reason they're not working is likely that the view doesn't exist in your system. If you don't have access to SSMS, someone on your staff should.
oh man! I have done a couple, so wonder why some work(ed) and some aren't? We don't have anyone available to do anything like that here, at least not by my request :)
Thanks!