chuckiecc
Members-
Posts
7 -
Joined
-
Last visited
chuckiecc's Achievements
-
Giving users the ability to import into tables.
chuckiecc replied to jimarch's question in Import/Export (on demand and scheduled)
-
chuckiecc reacted to an answer to a question: Giving users the ability to import into tables.
-
I'm not very good with Caspio and my developer resources are occupied with other tasks. Trying to figure out how to do this and/or hope to find someone that could assist please even perhaps do it for me, not sure how hard this is. Sorry if this post is a bit detailed. I'm just stumped here on what to do.. BUT we need this to work. Thank you for responding and reading if you are inclined to do so. Any help is greatly appreciated. Problem to solve- In our business we have a set of 4 tables that we record data to each time we interact with a customer. Each of the 4 tables represents an "encounter" with a customer of a different type. Our customers can in one visit to us, have all 4 services or maybe only have 2. These services take place usually in the span of about 2 to 5 days, but each of the encounter/services that are related to each other, are CODED with a unique encounter number. Our customers come back typically every week and could have all 4 services or 3 or... Just depends. Again the encounters, could span a two week period, but typically in 95% of the cases all fall within one week of a Monday thru a Saturday. They are coded for the encounter ID based on which services are related to that encounter. So an encounter is initiated and then closed. Again typically within a week but NOT always. Each encounter is time stamped/day date and coded with a unique visit id. So for one week for example customer "A" could have all 4 services with an encounter ID of "1234X" Next week Customer "A" could return and have only 2 services with an encounter ID of "1453z" for example. But each week during their interactions with us we produce these records into these 4 tables for the different things we offer. Again all with unique customer number/id, encounter id's and some other information regarding those encounters in the records in the table. Hope that makes sense.. We then take those encounters based on the week, and populate a 5th table as below. Usually on Sunday of that week. The 5th table- (billing file table) The 5th table is generated from a series of reports we run to create it. We run these reports weekly usually on a Saturday evening or Sunday for that prior week. This 5th table that is the combined data of the other 4. This 5th table is generated by us based on running a series of reports from the 4 tables, with some conditional logic we apply. This conditional logic "omits" intentionally some of the records in the 4 tables when it pulls to the 5th one. We then take the information in the 5th table and go through that manually and make small modifications at times, and then we transmit the modified information in the 5th table to our billing company. One problem- Remember our encounters have unique ids. So it is possible that an encounter can have one record or two in one week, then another record or two in the next week. BUT when we are looking at these by week, we would not know that per se. We can surely (and do) look at the data, and see that this customer A only has 2 of the 4 typical encounter records. BUT we don't know if the other two were omitted because of our conditional logic intentionally OR if the other two fell in the prior week. We look at the data in the billing file table and then modify this at times and transmit that data to the billing company. So we have now two files with data- 1) the 5th table with the encounters created based on conditional logic, and a file we sent to the billing company which is then loaded into another table (6th table (FILES SENT TO BILLING COMPANY). At times we intentionally omit SOME of the files in the 5th table (billing file) from some of the files in the 6th table (Files sent to billing company) for different reasons based on a review of the data for one reason or another. What we want to accomplish- WE want an easy way to do the following and hopefully this can be done is Caspio within a datapage. My consultant tells me he can't figure out how easily in Caspio and wants us to use a local excel file using v lookup functions. This maybe easier from a data manipulation point of view but in this way i cannot simply easily task someone to review and modify the data. We want a report/datapage that an administrator from our end can look at and compare the data from the 5th and 6th tables and see what we IN the original billing file and what was NOT sent to the billing company, for whatever reason. This would show ONLY that information that was IN the 5th table but NOT in the 6th table. Then if there was missing information in the 6th table, that operator could enter a new record, or pull the missing record into the 6th table and have the ability to change some of the information in that record prior to submitting it. example 1) if for encounter id 12345 there were 4 records in the 5th table (billing file) and only 3 record in the 6th table (billing file sent to billing company) it would ONLY show the missing record. example 2) If the records in the 5th table matched the records in the 6th table (i.e. records created equal records sent) then NOTHING would show in this report for that encounter number "123455" etc. example 3) If the records in the 5th table matched the records in the 6th table (i.e. records created equal records sent) BUT There were differences in the data on 2 or 3 fields it would show the data in the 5th table (billing file) and the data in the 6th table (billing file sent) and highlight the anomalies, and allow the admin to either append the dates/information or ignore the changes and then resolve this by ignoring it. thanks for reviewing this.. ugh..
-
Giving users the ability to import into tables.
chuckiecc replied to jimarch's question in Import/Export (on demand and scheduled)
I guess perhaps my question is a bit different that your? not sure. Although I would like a datapage to be able to enter this info, OUR concern is that we receive .csv files, with data that needs to be added to a table. Easy enough. BUT the issue for us is that we receive this data multiple times in a day and SOME of the data we receive in a day is already in the table we want to append to. WE have a unique identifier in our records/fields so that we can make sure our data integrity is ensured. So while the import feature works fine and isn't really an issue for us, the ISSUE is that there is no way (that we are aware of) for us to CHECK the records of the proposed upload vs. the data already in the table and either a) identify those records that are duplicates and NOT import them, but import the others, or b) reject the entire file and list WHICH records already exist? or c) allow us to append the data, bu only append the non duplicates So there may be a way to do this with the import tool, but if there is I can't figure it out.. Any ideas anyone? -
Giving users the ability to import into tables.
chuckiecc replied to jimarch's question in Import/Export (on demand and scheduled)
Jim did you solve this by chance? We have the same issue with the nuance of adding a unique record check for the upload such that IF the record/information exists that one out of the bunch are NOT uploaded, yet the others are allowed.. I don't want to rely on the professional services group, would rather know how it was done if I can ask.. thanks -
we manage multiple client programs for them and they perform some tasks. This issue surrounds assigning a serial number to their individual members each week. Providing that those members of the client have accomplished a small task we give them each week answering a few questions. IF they have answered the questions, then they are "qualified" to receive their serial number. If they have NOT answered their questions, then they are "NOT Qualified" to receive their serial number and they cant enter the number in the field.. Works great no issues. If someone shows up to get a serial number, and they are NOT qualified, all they have to do to "fix' this is to log into their portal and answer the questions we give them and then their status changes to "QUALFIED" One more nuance is that we allow the members of the group to answer the questions multiple times. Their "answers" (validation/qualifications") are good for 7 days as set by a parameter. But we let the users "stack up" answers to the questions if they want. It doesn't matter to us which iteration they choose when assigning a serial number to them. only that they have qualified. We need to create a table that shows the administrator of that client two things: 1) those members of their group that are QUALIFIED to get their serial number and, 2) those members who are NOT qualified to get their serial number. but registered in the program. Here is the problem- the individual clients users are either idiots or very clever. They have found a way to exploit our registration system such that they have registered multiple times under multiple alter egos. Why I have no idea in the world. Yet they have. Worst yet is that one member of a client: for example John Smith DOB 1/1/1980 could have registered 4 times! with different emails. Ok kinda hard to prevent that. BUT if John Smith can't remember which alter ego/email address he wants to use/password combination, then he MAY log in to any of his 4 alter egos and answer the questions. Which isn't the worst thing in the world. HOWEVER what has happened in real life is that for sure John Smith has registered 4 times.. BUT for some reason John Smith in 3 alter egos, has properly associated with the specific client group, while his 4th alter ego has NOT properly associated with his Client group. This alter ego is "unassigned". Because we use authentication based display to ensure that a client only sees its members, then if John Smith's alter ego #4 is the one he answered the questions for, he gets to the top of the line and the Client administrator sees his name on the list (3 times mind you) as being NOT QUALIFIED. John Smith KNOWS he has answered the questions. Further frustrating is that John Smith himself has created this issue arguably. So he argues with the administrator, "no I just answered the questions". Which he did, but the administrator can't tell that because they (as the client) can only see those members associated with their individual group. We can't let the system admins from the client see others, and its hard to train a bunch of people to know what to do..!! So how can we solve this? questions- 1) is there a way if one alter ego is properly registered in group "A" for john smith and another alter ego for John Smith carrying the same DOB + first last name and maybe cell number? is registered in another program/group, that we can SHOW the administrator that John Smith is being shown as registered in two groups. THIS WOULD MEAN THAT THE AUTHENTICATION VIEW WOULD HAVE TO HAVE AN EXCEPTION ONLY IF THAT PERSON IS REGISTERED IN MULTIPLE GROUPS TO SHOW WITHIN EITHER ONE OF THOSE GROUPS? Then they could alert John to correct his registration and associate his 4th alter ego with the proper group. 2) we are having a hard time showing those members of a group that are qualified to get their serial number and those that are not on the same table. We are told by support that this is because our account does not support cascading tables and we have to upgrade to get that which is prohibitively expensive for us as a small company. We temporarily solved this somewhat by giving a tab one with all members of the group and the other one with those of the group that are qualified. But it would be nice to combine those into one table would be preferred. 3) we ARE able to build a table that shows both qualified and not qualified at the same time, but doesn't parse out multiple views or multiple identities/alter egos.. Is it possible to have some type of filter that shows in this table ONLY one alter ego for someone with the same DOB + first + last name for example so that IF There are 4 alter egos registered, only one will show such that our data downstream over time becomes more streamlined? but this then brings into play the issue of john smith above, having 4 alter egos. If we show one, then the one that he happens to log into that week will need to be the one that shows. UGH WE have so many users now like this and so much historical data frankly its a bit of a mess. We have tried to employ measures to narrow the multiple alter ego/registration going forward but honestly don't think we can clean up what we have.. Any ideas here would be most welcome' thanks
-
We are looking for an api that will behave with Caspio to validate Emails when our users register. We have successfully gotten dbounce to work, however the validation 'check' renders above the header on our datapage and we cannot move it to elsewhere in the page no matter what we try. Can someone help with this or, reccomend an api that behaves better with Caspio? easiest/cheapest/best etc../fastest thanks
-
chuckiecc joined the community
-
we are trying to figure out if Caspio is an option for us and need to capture barcode values into a web based Caspio form.? Currently we are using jotform to capture that data which works fine, but we need to manipulate that data, which is a shortfall we have in jotform. how would we use Caspio to capture the information off of barcodes using the native scanners in cell phones mobile devices. thanks