Progress Report 3

 Alright. Progress Report 3.

To start. One of the problems with scrubbing these files, is that I don't know which File should be chosen for the Mineral Owner that should be scrubbed. Therefore I should  look into either making an auto search for like terms. "Mineral Owner", "Account Owner", Or just have the user select which one should be scrubbed. Which is preferable. 

Right now I have the GUI practice throwing up a ratio button option. This seems to be a good option as they just have to choose one of the headers. How I put this into the GUI class might be a little bit more interesting. But we'll see where it goes. 

 Other things to think about are using filters. And taking which ever choice this is and matching it to the Salesforce download button. Maybe even putting in a link that brings you right to the report that you have to download. The amount of options for connecting to Salesforce are vast. I love the back end excel plugin, but that doesn't always work on every one else computer. Another option is trying to hook in with an API. But as I have found out in the past. It requires an additional license. For the most part, I have found myself coding against Salesforce to make it so that you do not need to pay Salesforce more money for the options. 

Enter in the idea, that It should just bring you to the reports page, which anyone can access. And / Or just have the file saved in a folder that the person refers to.... I'm thinking linking it up into Salesforce reports folder is the best option. Make it dumby proof. Those that know what they are doing could just modify the code to pull the base report account quicker.

While searching for radio buttons I found a much smoother solution. Just make it a select button. And use the looping button. Makes perfect sense. I might even go back and continue to modify the value's entered.

https://www.python-course.eu/tkinter_radiobuttons.php

Nice link right above.The style for this project has mostly been testing the GUI on the side. Getting an understanding for it. Then converting it over into the main program. Compartmentalizing these new bits of code seems to be the best route. Eventually, I think it would be nice to keep the class in their own file. And call it from the python package. It would be great to go even further and develop a folder of my own classes that I have made. So that I can call them in when I need to user them.

Moving this code over to the classes seemed to be a bit more difficult. The .get() function or or the self.master.StringVar() is not returning what we want. The solution is a bit janky right now. I am essentially putting a separate GUI into the the class to create the looping button. I'll have to touch up on that a bit later.

Now it's really time to look into the other. Code, and get it to start running off of that. And throwing in the different look ups. Finally Starting to get to more functionality, And less GUI practice.

UPDATE:

Turned the Looping GUI into it's own class. We'll definitely have to do this process again. And maybe even rewrite it more to make it more usable. But I am finding that I am learning a lot as I go forward.

Which brings us into the the next learning subject. Pandas. Which I ironically took out from earlier. Right now I have the file in a list of strings... Which is alright.

 

Previously, the code that we started with. Was designed for a midterm project, which meant throwing it in and out of lists, using dictionaries, etc. Which is great and all, but not sure that we'll have to use the same code here. Lots of options.

 

Twist it, Turn it, Bop It. That's how I view dealing with data. Just twisting it into another form. Turning it with filters, the bopping it by throwing some functions down it.

The files that this program will be dealing with has a lot of duplicates. The original code we put it into a dictionary, then changed the name. For this project we'll just fix the names first. Then look into filtering off a list to see if we can return the account numbers. This is one of the most crucial steps. The general public has no clue how to vlookup, xlookup, index match. any of it. In fact, that's why we're writing this more complicated python code.

The relief that we're getting some use out of the original code! Let's just quickly test the output with just the scrubbed name. And it's going through the save file option! Few things to fix. But nothing major. This is a file in which we can work with. And it's getting scrubbed in seconds.

After a few tweks here and there. I have my looping headers working great! Functionally, at least. I could use a little extra padding, and maybe even a scroll bar. But I'll have to get further along before putting on the glitter.

Loving the uses of classes. It is really simplifying the code below. Now I just have to figure out to do the look up through these fields now.  

Just a few touches away from actually taking these names and splitting them into first name last name etc. Progress is being made! This program is actually going to work. It's going to be fun building out the functionality more.