Name: InsideTrack to the Unified View-Import for Impact
Uploaded: 2026-04-14T16:15:54.454Z
Duration: 38 min 32 s
Description: InsideTrack to the Unified View-Import for Impact

Transcript for "InsideTrack to the Unified View-Import for Impact": Perfect. Alright. Thanks, Tanya. Let me move us to the next slide here. Alright. So, before we get into import, I just wanna quickly update you all on our unified view timeline. So just wanna mention here, the timeline has not changed. We are still focused on working towards unified view in 2027. This year, we're focused on our core your core business functions, which is what you'll continue to see in these inside track sessions and also in our town halls. But we are specifically focused on gift processing, also data management, so helping you manage query and also exporting your data, importing your data, and online data review transactions. All of these are key to your core business workflows to help you make the move over to WebView. This road map is what we presented back in November in the product update briefing, and we've made a lot of progress here, including releasing the first phase of gift batch for parity with existing web form batch. So we'll share more of those updates and more updates that we've also recently released and what's to come as well as what's next for RNXT in the spring customer product update briefings that are coming here in just a few weeks. Okay. So let's get into why we're all here today, which is import. So I'm going to be taking you guys through what's being developed today and also give you a view of what the future of import is going to look like in WebView. Okay. So import in WebView, it's not just a an updated way for you to get your data into the system. This workflow is representing a shift into how we're thinking about data management in RNXT as a whole. With import in WebView, you're going to be able to insert and update records in a single file, so without having to choose an import type upfront. What this means is behind the scenes, we're going to read your file headers and use the data in your file to understand whether each row is an insert or an update and which records and fields those change those changes apply to so that one file can be handled one file can handle all of your updates and inserts across multiple record types. We're also going to be introducing a new import user interface in WebView, which is going to be designed to be easy for you to use and support completing imports reliably at scale, whether you're running a one time import or doing this as part of an ongoing import workflow. Your imports are also going to be running asynchronously in the background, which I think many of you, if not all of you are going to be most excited about because this means that you're going to be able to keep working in RE NXT x t while that import job processes. So there's no more work stoppages while you're waiting for an import to finish before you can move on to something else. You're also going to see clearer validation and error handling, which is going to make it easier for you to identify and fix issues and things that need attention with your imports. And, also, import in WebView is being built with improved reliability and performance. This is especially important for your larger datasets and those long running jobs to make sure that these imports can scale with your data and minimize the amount of disruptions that you get from importing such large files. So when we're talking about import in WebView, I wanna call out that you're going to have two ways to bring in your data. You'll have the import UI where you can easily upload your CSV files directly in WebView, and this is gonna require no technical setup beforehand to be able to use this functionality. You'll also have the ability to import via the API, which is essentially what's providing the foundation in the background for import, and it's also what is enabling integrations with partner applications and other customized solutions and automated workflows that you might have in place. But let's go ahead and talk about the import UI. This is what you're likely going to use to perform your imports in WebView. So with the import UI, the goal here is to make getting your data in as simple as possible. So when you're running an import, you're going to upload a CSV, and then like I mentioned a minute ago, the system is going to handle the rest. So you'll no longer need to decide upfront whether something is an insert or an update or what import type you need to use. Like I said, behind the scenes, we'll be looking at your file headers and the data in the file to determine what actions you need to take so that single file can handle inserts and updates across your multiple record types, which is going to minimize the time you need to spend setting up your files ahead of time before running that import. As we expand import, you're also going to be able to import all supported record types directly in the UI as those become available. So eventually, this is going to reduce your need to hop back and forth between WebView and database view to perform those imports as we're delivering more functionality and import to you. I'm going to touch base just in a few minutes on the timing of those additional import types, but wanted to make sure I called that out here just so you guys are aware. In terms of your import fields, those are going to be automatically mapped based on your file headers. So that should feel familiar to you if you're used to how imports work in database view today. And on the gift side, you're going to be able to import directly into gift batch. And then from there, you'll be able to review, edit, and manage your gifts in bulk from the gift batch grid. The gift batch update functionality is also coming soon, so we're actually working to surface that in tandem with your ability to import into gift batch so that that way you get all of that great functionality at the same time to make it a really cohesive and, cohesive workflow there. So this is all coming together to provide you with what we keep talking about as the simplified modern import workflow that's going to be more efficient for you and it's also going to help save you some time. Okay. Before we move on, I wanna just take a quick second to walk you through a prototype of the import UI, just to give you a feel for what it's going to look like and feel like in web view. So let me go ahead and stop sharing here. And share here. Just give it a second. Perfect. Hide this and make this bigger. Okay. So in web view, the import UI is going to live under a new data management section in the left nav. And then once you click on import, the import UI page is going to look something like this. When you're on this page, you'll have your list of previously completed imports. So, here we have one import already, which you can see is import number 15. But on this page, you'll also have the ability to start a new import and you'll have the ability to filter and sort on your past imports and also see various data points about those past imports that you've completed. So let's see here. Let's mock up running a new import. Once your import file is ready to go, you'll come to this page and you'll click on create an import. Doing so is going to open a modal where you'll then select the file you've prepared, and then you'll click Next. When you do that, it's going to bring you to a field mapping screen, which is going to show you the column headers from your file and the RE NXT fields that we've mapped them to. So in this example, everything has mapped, so all your fields will import into the system. But if for some reason a field does not map, you're gonna see a screen that looks something more like let me pull up this other one, like perfect. Like this. So here, you can see that in this situation, one of your headers did not map. So when something like this happens, you have a couple different options. You can either still proceed with the import knowing that the data in that column isn't going to come through, or you can go back to your original import file, update the header to an accepted field, and then start your import again. Let's go back to this example where everything has mapped. Mapping looks good here. We want to move forward, so you would go ahead and click Import. From there, the import is going to kick off and it's going to process in the background, and so you'll be brought back to this import page while that import processes. Because the import is already complete in this example, you can see that that import was import number 16 that we just ran and it is appearing in our list. For this import, we can see that there were 200 rows in the file. Of those 200 rows, a 198 of them imported successfully and two of them did not. So. for those two that were not successful, been chat's been going. to appear in an exception up, file, but let's go ahead then just knock some of these out and get started. the lower right. You'll also be able to access feel exception has got a lot of concern around, it is we're also going to have a way for you to access. that exception file at a later time from this import? row are three. parts to this question. Can they validate before import? you download that exception map, manually? you're going to see something similar to they get. exception query This is the exception? file that was produced the first one previous import number 16. This exception file is essentially the same CSV file as your original file, but it's containing only the rows from the original file that have issues. We also added a column here to the beginning of the exception file that helps us identify how rows in the exception file relate to your original rows in your original file so that it correctly connects when you reimport these fixes. We also. added some warning text here just. alerting you to not mess with any of the, values in this column because then that messes with the file and that can make for an invalid import. In column a, we do also list the errors that occurred in those original rows, so they indicate the problems here that need to be fixed. The benefit of the exception file is that it's only identifying the rows that need to be fixed. So that way, rather than having to navigate back to your original file, making the fixes there, and reimporting your full file, this condenses your original file to only the errors that still need to be. fixed. So it is a smaller reimport of those fixes He won't keep these updates. exception query after import. In this situation here, we can see that for Todd, there is, an invalid state and an invalid ZIP code. And then for Danielle, there is an error for the postal code required because the ZIP code was missing in the original file. So in this case, let's pretend we go ahead and we make those changes directly in this file. So we'd update the state and the ZIP for Todd, to this next would. add a to be able to query Danielle updated was missing. import records. We'd that still happening? that exception file. We would then go back to the. import. page. So that was an easy answer. create an import, Okay. and this time, you would choose the recently records be linked to online you just? you just saved, and then you would run the import. After importing that exception file, you can see now that. If we don't have an answer to the, appears in your list. today, guys, In this know, case, we'll be doing a recap, log, of course, and that those two your unanswered processed. questions there as the top questions rows, answered in that in that blog. successful we might not be able to answer, everything today, confirming that the data get you two answers. exceptions was imported Can. we give the import file a name, so it can be used repeatedly? where you did an import and your original import had no exceptions, When you ran that import, it would look something more like import 15 where all rows were read, all rows were imported successfully, so there would be no exception file that you needed to make changes to. K. Let me hop back to our deck here. Okay. Alright. So now we've walked through what's coming for the we have a little, message from David saying, and I'm sure think guys have a saying of is. output query, I do, have some FAQs exception at the end, So, but we'll still follow-up on collecting that's the quick answer that that I'm to at the end now. of today. But I wanna cover an identifier to indicate an import is done in database working or web, view? which we're so we're starting with the import API. This is what, like I said, is laying us laying the foundation for everything that we're building in import and web view. So I wanna just give you an update of what we've been working on so far. At a high level, the API is simply a way for systems and tools to talk to each other. In the case of the import API, it's giving us a single scalable engine system submitting, validating, and processing these large volumes of data. Today, ID an acceptable ID? Should couples be imported together or separately? the consistent the consistent validation and error handling that we talked about earlier. So that's providing you with structured feedback so issues can be, more easily identified and fixed, which is especially import, like I said, for your larger imports. And all of this is available currently in a partner only EAP that we kicked off on April 7. So we're making some good progress here. And let's see. Hopefully, Okay. this answers, some questions I'm starting to see in the chat, else on spouses. global update. Will there be capability I import we've covered a? lot already today, but I did wanna take just a few more minutes here to talk about what's next for import and web view. So coming soon, we're introducing duplicate detection, which is going to help you identify and resolve potential duplicate records when you're running your imports to prevent you unintentionally creating duplicate records and helping keep your data clean. We're also going to be servicing. the ability to apply updates the import file be? Is there, records guess, maybe, and, associated limit you're saying? contact fields without creating new records since today, what's currently in the EAP is insert only, so we're gonna can add that. the ability to update as well. With duplicate detection and the ability to update, both of those are going to be available via the API first, but all of this functionality will become available via the UI once the UI has been created in WebView. So you might be sensing a pattern here because I keep reiterating this, but I just want to make sure. it's clear. that the functionality Would you be able to revoke an import if you made a mistake? going to be available via the UI too once the UI is available. We're also going to be introducing the ability to import directly into gift batch, so you'll have that centralized location to manage your mass gift entry there. We have the import UI, which will be coming to life, delivering the experience that I just walked you guys through a minute ago. We're also the part to be expanding get their workflow. coverage to support additional. constituent import types, which includes we be able to import, constituents relationships, and custom fields at the same, time, in one import? and other solicitation, Yes. solicitation You want to. put it. And then beyond constituent and gifts, because. we're just starting with constituent and gift, but you obviously need know anything about cons types to do your full business core the. exception report? We're gonna guess it wasn't in your in your, import types. demo. Do you know if that'll be included? but not limited to campaigns, funds, appeals, and events as well as others. And then you'll also be getting access to, global change, which we're calling the bulk add, update, and delete capabilities. So you'll still have the ability to support those high volume creation and modification of records directly in WebView. Something that's missing from this what's next right now, but I still want to make sure that I call out while we're together today, is additional import functionality that you might feel is missing, like. showing import progress, Does this mean import will be able to determine your import constituent well as the ability to cancel and import, needs to be created? file preview, So can it defer between validation two? prior to importing. Our focus right now is getting the core functionality of import and those core import types into web view, and then we'll bring in the additional import functionality that you're looking for, hoping for, expecting to see. Before we open it up to questions in the chat, I am going to walk through a couple FAQs that we've seen pretty consistently that we'll answer first, and then we'll move on to chat questions here. Okay. So first question that keeps coming up is how can I sign up for imports early adopter program? So the API EAP is currently available to a small number of partners, But if you are an API user and you're interested in the API EAP, please reach out to me, and we can chat about getting you either access to this current API. EAP or a wave two to get you that functionality, mapping. Lots of lots of we are in need. of API feedback as well. it doesn't map correctly? We have you be lot of to change the field like they can do now. in database view? for that, as of right now, the registration for the UI EAP is closed, but we do expect to kick that EAP off in q three. So I'll keep you guys posted on the, timing of that EAP. But if you have any questions there, you can still reach out to me, and we can chat and, figure out some next steps there if you're interested in the EAP. Next question. Will WebView import replace the need for partner solutions? So short answer here is no. We're providing the ability for you to import into Razer's Edge NXT directly using the, user interface or via the API, but partner solutions are still gonna be needed a requested you have any need for. It's it's it's it's a hot top of what we're going to be providing. So. We've been working very closely I see there are questions they're building out their modern. solutions, and like I said, they're part of an EAP today for the API, in a few short weeks. It's the weeks want, to make that clear. that this is not replacing the need for partner solutions. So there is going to be, a lot more information that would be given during, Are you still going to be able to use database in database well as, for import? a more determined, yes. timeline. As of right now, just a few more weeks be able to continue to use that information. view for import. As this functionality have to mess with web view, zeros provide? guidance and help docs to help you take advantage of that new functionality. not sure what that means, as I thought maybe this might. out, you'll continue to be able to run imports in database view as well as in web view as that functionality becomes available. Will I be able to identify existing constituents without an ID? So import in WebView is going to require a unique identifier, either the constituent ID or the import ID in order to match the incoming data to the correct record. But if you don't have an ID or one. isn't provided, we do have that duplicate is something we might wanna kind of noodle on from the list. potential there, be an easy access ID is going to be needed to make that import headers and the fields existing map. to? Are we migrating over import history from database view? So, no, we're not going to be bringing over, your import history. The data that you update is going to update as expected across. both views. So if you, import and database view has an export do an import allows database to access, additional fields import update available going to query or expert. data in both database view and in web view. available in WebView? the import history is specific to each location, so you're only going to see import history where that import was initiated. Will existing imports that we built in database view be available in aria NXT? Like I mentioned with the additional import functionality, right now, we're focused on bringing that core import functionality into web. view feel like you touched you this one, actually just to reiterate import. also, are once that's in place, all our index to explore avail over the existing import including custom database? view you touch on that again? to what we did with other functionality like query. We just want to start with the core functionality first, and then we'll pivot our focus to bringing over those existing imports. Alright. Will WebView import keep the option to create an import file? So we are going to leverage the new functionality that's available in query and export and use that as a way for you to create your import files. And we're also on the flip side, working to ensure that the fields available via the export from import functionality that you're used to in database view today, making sure that the fields that are available from that functionality will be available for you to. query and export on in our NXT. table entries you'll have time you need to? complete your business processes fully in WebView, and you'll. have access to those fields that you need to do so. So wanted to call that out, but stay tuned for more updates here. Then we want keep you posted on progress as part of. our import rollout. Okay. And then last it, flag will I be able to import exception? spreadsheets from outside sources and vendors? Short answer here is yes. That's still going to be possible. You'll be able to import those think I lost Internet there for just a second. But you'll. be able to do just put that as that's the bulk. the API via CSV file. You can also do it through the API via JSON, but, most likely, you're gonna be using CSV files there. Alright. That's it. for my FAQs. Let's, see. Will we be able to have separate, folders will yeah. the import section? Yeah. So on the validate, yeah, If it's a new in three parts. The validation CSV, like, file, for the workflow still have showed you guys today, a constituent is, a very condensed, simplified ID, workflow do you have to add it manually? get a feel for what it's gonna look like. Validation is obviously needed. That's one of the things that we are aware of. I expected that to come up in the EAP as well. So right now, in this workflow, validation is not included, but it's going to be included once import is available. Right. So right now, v one, we have it as the automated mapping based on your header. fields, This is about previous know that. the need for use the same manual mapping and just switch out there, the CSV so you don't of to start from scratch each time? mappings work. It's easier to be able to make those changes in the system versus having to make sure your headers match. So while that might not be available in b one, we're still working through the specifics there. That's the personality that we plan to have on our road map for down the road. Okay. When the import after import. ahead. Go ahead. Yeah. I don't have an answer to that specifically. That's something I can connect with David. on afterwards just to see how that thinks there is a management terms of being able to, query how will. you confirm that know? you'll be able to run a query to see, like, what was imported. And so from there, you can cross reference, like, what was missing. But that's a question that I can follow-up on afterwards. Be able to query on updated import records. Yes. They'll be able to do that. Okay. Because there's been a lot of chatter about templates. So currently, in database have, an answer to, import templates can be deleted. but I can find out and circle gonna. be preserved where we they can go back and check imports, if there are any questions about the data? And can you I know there have been a lot. I've seen the word templates in chat a lot. Anything else you wanna elaborate on templates would be great. So, that's great feedback. Right now, we don't have it set up for you to to be able to add an import file name. I don't know why we wouldn't be able to include that as part of your import setup, so that's certainly feedback I could take back. I understand the need there and being able to leverage it. You will be able to see, like, the file name in your list, but I understand that that's not as conducive as being able to import or to be able to list your be able to name your import and have that show in the first column. So that's good feedback we could take back. Okay. Can we adjust automatically assigned headers? K. No. So right now, there is no identifier to distinguish between the two. I don't believe. I can certainly circle back with, my team and confirm. That's just where I guess I can see, like, I wanna understand more, like, why you'd. wanna differentiate the two, but you'll know able to cross reference on global change. database view and, web view to see where the import was run. add and global change function? That I I'm not sure. I don't wanna give you the wrong answer. I know, right now, constituent ID, import ID, system record ID, I don't think is going to be an acceptable option, but we'll circle back on that just to confirm. And let's touch one more time on delete functionality. Is that a possibility It shouldn't future? matter. I guess it depends on what you're trying to do in your process. But with how we're how we've changed the import workflow, you can have couples in the same import file. And depending on what you're trying to update, it's going to be able to update each of those individually. If you're trying to create two new records, both having that relationship, you'll be able to make that relationship in the same file as creating new constituents. So that falls. under relationships. I can look back at we're out of time, everybody. specifics are, under, relationships. for don't have that list in front of me. for the fourth if you're able to do it in database view. today, you should be able to do it, with WebView, import as part of relationships. I'll confirm, though, that we're building and just. make sure that we clarify that. If you don't know where to start, we suggest with the razor's edge NXT resource center. It really is kind of the hub that links to all of these items, Yeah. There's gonna be a limit. Let me see if. I can look it up really quickly. new, comes out every Tuesday don't have the date let me yeah. eastern. We can add that to the follow-up I would pay attention clear. to. Our product update are, gonna have just a limit are, like, next, month. They are one of the most important, know that it's gonna limit the attend size. all year. It's more do have the registration how long it's gonna doc us, on the back end to. run have file, some I'll I'll confirm that cool new tools for y'all. to use to, keep up with exactly what we're doing with the future of Raiser's Edge NXT. But thank you for joining us today. Alright. So that's some of that functionality your time, right now. we will see you at the not included, update briefing. the cancel ability is, guys. coming, because in these situations, I understand that if you've kicked off an import and for whatever reason, there's a mistake or you decide you don't wanna run that import, you chose the wrong file, you wanna be able to stop that. So that is going to be coming as part of this import workflow. Yes. You will be able to do that. In the exception, I'd have to see, like, the question here of what the situation was. But if if in the exception file, there's an exception around the gift, that would be included. It wouldn't be included if there wasn't an exception in that situation and also depends on what the exception is. If it's a hard exception for gift, that'll show up in the exception file. But if it's a soft exception for whatever reason, that it'll still go through, and that will show up in gift batch, and you'll be able to manage things there. Yeah. So similar to the functionality in database view today where you have the option to, select, like, update or insert, if something's not available with these or if something doesn't already exist. With how import's going to work today, it'll be able to understand if it needs to be an insert or an update directly from your data in the file. So on the back end, it's gonna read, your system and be able to determine, does this constituent already exist? If it does, you you should have a constituent ID in your file. But if for some reason you don't, that's where the duplicate detection comes into play. So we'd be able to call out, like, hey. It looks like you don't have a constituent ID. You might be trying to create a new record for an ex a constituent that already exists. So you can then determine, do you wanna move forward with the import? Or, yeah, if you wanna move forward with the import or, if it's going to update the existing constituent with that information. Yeah. Right. So, that comes into the ability to, like, manually change your mapping in the UI. Right now, in this first v one, it's not currently planned, but if we continue to get feedback that it's needed, we'll reconfigure and provide that. The initial workflow was that it was going to map based on your header fields and that those would have to be specific based on help documentation that is provided. But in the chance that